Frontier is listed as active in the registry but did not answer our last check. It exposes 3 tools.
Discover Frontier inference capabilities and read sanitized usage through read-only tools.
Frontier does not always answer
Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.
claude mcp add frontier --transport http https://openfrontier.dev/mcphttps://openfrontier.dev/mcp[mcp_servers.frontier]
url = "https://openfrontier.dev/mcp"{
"mcpServers": {
"frontier": {
"url": "https://openfrontier.dev/mcp"
}
}
}{
"servers": {
"frontier": {
"type": "http",
"url": "https://openfrontier.dev/mcp"
}
}
}Available tools 3
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
get_capabilities
list_models
get_usage
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://openfrontier.dev/mcp | streamable-http | answering | 29 ms | 5 min ago |
Alternatives to Frontier
same job, measured the same wayRead-only matching from user problems to public Evercraft capabilities.
Discover and execute authorized API capabilities through QuoAPI policy, routing and billing.
Read-only discovery of Framekeep capabilities, security boundaries, and public resources.
Discover MCP servers and packages with cited capabilities, provenance, and reference facts.
MCP-first read-only discovery of your infra & SaaS landscape as MCP resources, tools and prompts.
Real-time agentic newsfeed for MCP tools and capabilities
Discover, hire, and verify real-world physical capability through MCP.
Access Pollinations models and API capabilities through agent tools.
Frontier — questions
Answers built from our own checks of this server.