Content Tools
epicalgorithms.com
Provides access to Epic Algorithms' published articles and case studies, enabling keyword search and full-content retrieval.
ENDPOINT 1
https://epicalgorithms.com/mcp
MCP server metadata
- Name
- Epic Algorithms
- Version
- 1.0.0
Known tools 6
search-postsSearches published Epic Algorithms articles by keyword and returns matching titles, slugs and excerpts.
Inferred read-onlylist-topicsLists the categories and tags used across published Epic Algorithms articles, with a count for each.
Inferred read-onlylist-case-studiesLists the projects Epic Algorithms has delivered, with the client, industry and year for each.
Inferred read-onlyget-case-studyReads one Epic Algorithms case study in full: the client challenge, the solution built, and the outcome.
Inferred read-onlyget-pageReads a page of the Epic Algorithms website as markdown: what the company offers, who it is, how to reach it, and what it is hiring for.
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.epic-algorithms]
url = "https://epicalgorithms.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"epic-algorithms": {
"type": "http",
"url": "https://epicalgorithms.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: epic-algorithms
Remote MCP URL: https://epicalgorithms.com/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": {
"epic-algorithms": {
"url": "https://epicalgorithms.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"epic-algorithms": {
"type": "http",
"url": "https://epicalgorithms.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "epic-algorithms",
"transport": "streamable-http",
"url": "https://epicalgorithms.com/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.