Fentaris is a centralized MCP proxy that unifies multiple MCP servers behind a s
Fentaris is a centralized MCP proxy that unifies multiple MCP servers behind a single controlled endpoint, with stable routing, policies, identity, middleware, and rate limiting.
active Production-safe Score 96/100 http no auth
At a glance
| Endpoint | https://mcp.specification.website/mcp |
|---|---|
| Source | https://github.com/Fentaris/fentaris |
| Transport | http |
| Tools | 6 |
| Auth | none |
| First seen | 2026-06-16 00:14:14 |
| Last checked | 2026-11-17 21:44:50 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 256 / 425 ms |
| Last successful check | 2026-11-17 21:44:50 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (6)
search— Read-only, deterministic full-text search across every spec page. Ranks pages by weighted keyword matches in title, slug, summary, and body,list_topics— Read-only. Return the canonical list of spec topics, optionally narrowed by category and/or status, each with title, status, category, summaget_topic— Read-only. Fetch the full canonical Markdown for a single spec page by its slug: YAML frontmatter (title, status, category, sources, relatedget_checklist— Read-only. Return a Markdown checklist of spec items grouped by category, optionally filtered by category and/or status. Built for site audiget_categories— Read-only. List the ten top-level spec categories with their summaries and topic counts. Takes no arguments. No side effects; categories areget_changes— Read-only. Return the spec's change history — new pages, status promotions/downgrades, substantive rewrites, and removals — newest first, ea
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:44:50 | ✓ | ✓ | 232 ms | 94 | active |
| 2026-11-17 21:29:46 | ✓ | ✓ | 183 ms | 94 | active |
| 2026-11-17 21:14:33 | ✓ | ✓ | 168 ms | 94 | active |
| 2026-11-17 20:59:13 | ✓ | ✓ | 190 ms | 94 | active |
| 2026-11-17 20:44:13 | ✓ | ✓ | 297 ms | 94 | active |
| 2026-11-17 20:29:12 | ✓ | ✓ | 407 ms | 91 | active |
| 2026-11-17 20:14:07 | ✓ | ✓ | 325 ms | 91 | active |
| 2026-11-17 19:56:15 | ✓ | ✓ | 384 ms | 91 | active |
| 2026-11-17 19:41:08 | ✓ | ✓ | 340 ms | 91 | active |
| 2026-11-17 19:25:49 | ✓ | ✓ | 312 ms | 91 | active |
| 2026-11-17 19:10:45 | ✓ | ✓ | 151 ms | 94 | active |
| 2026-11-17 18:55:38 | ✓ | ✓ | 177 ms | 94 | active |
| 2026-11-17 18:40:31 | ✓ | ✓ | 341 ms | 91 | active |
| 2026-11-17 18:25:25 | ✓ | ✓ | 272 ms | 94 | active |
| 2026-11-17 18:10:09 | ✓ | ✓ | 151 ms | 94 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://mcp.specification.website/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/mcp-specification-website-mcp # JSON