Other · Remote MCP server
Frontier Reference
Frontier-design reference: file formats, converters, definitions, sensors, companies, design jobs.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
so.falcon/frontier-reference- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-08-06
- Updated
- 2026-08-06
- Publisher
- so.falcon
- Namespace
- Namespace verified by the MCP Registry via the domain falcon.so · how
- Website
- falcon.so/resources
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://falcon.so/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- falcon-frontier 1.0.0 · protocol 2025-06-18
- Tools discovered
- 7:
search,get_definition,get_company,list_design_jobs,identify_format,compare_formats,convert_file - Checked on
- 2026-10-05
How to connect Frontier Reference
Frontier Reference is a remote MCP server: there is nothing to install. Its endpoint is https://falcon.so/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Frisian MCP (Django)Your DRF API as MCP tools - 1,800 endpoints become 16 dispatchers, permissioned by Django. | Remote · HTTPLive check: ✓ handshake |
| FriskScreen the counterparty of an x402 payment before an agent pays it. Runs offline by default. | Local · stdio |
| FrogletRun local Froglet verifiable compute, signed receipts, settlement, and service publication. | Local · stdio |
| FrontierDiscover Frontier inference capabilities and read sanitized usage through read-only tools. | Remote · HTTPLive check: ✓ handshake |
| Frontrun MCP ServerTrack what 1,000+ VCs follow on X to surface startups before their round. Signal for AI agents. | Local · stdio |
| FrugalThe open routing layer for AI tools: tool calls routed per policy, decision on every result. | Local · stdio |
| FTX MCP - FactoryTalk Optix MCP ServerMCP server for FactoryTalk Optix: author, preview, and verify Studio changes via the emulator. | Local · stdio |
| FudgeBuild websites that look designed, not generated. Fudge gives AI real websites to study. | Remote · HTTPLive check: sign-in required |