Security & Testing
tagmachan.com
Search and retrieve security blog posts, projects, CVE research, and threat intelligence from tagmachan.com.
ENDPOINT 1
https://tagmachan.com/api/mcp
MCP server metadata
- Name
- tagmachan-mcp
- Version
- 1.0.0
Read-only MCP server for tagmachan.com, the site of security researcher Tağmaç Han. Use search_content to find blog posts, exploits and CVE research; get_page to fetch a page as markdown; get_threat_feed for Fed0gaT IP/hash/URL blocklists. All content is public — no authentication needed.
Known tools 4
search_contentSearch blog posts, projects, exploits and CVE research on tagmachan.com by keyword (matches title, description and category, English and Turkish).
Inferred read-onlylist_contentList all blog posts and projects on tagmachan.com with titles, URLs and descriptions.
Inferred read-onlyget_threat_feedFetch the latest Fed0gaT threat intelligence blocklist (aggregated from Turkish NCC/USOM and other sources).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.tagmachan-mcp]
url = "https://tagmachan.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"tagmachan-mcp": {
"type": "http",
"url": "https://tagmachan.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: tagmachan-mcp
Remote MCP URL: https://tagmachan.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"tagmachan-mcp": {
"url": "https://tagmachan.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"tagmachan-mcp": {
"type": "http",
"url": "https://tagmachan.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "tagmachan-mcp",
"transport": "streamable-http",
"url": "https://tagmachan.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.