mcp server
frontier-reference
Frontier-design reference: file formats, converters, definitions, sensors, companies, design jobs.
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Registry entry last updated 2026-08-06.
What this server can do
7 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
compare_formats(a, b)- Compare two file formats (by slug, extension, or filename) — extensions, category, and a verdict on when to choose each. Use for 'X vs Y' / 'difference between X and Y'. Required: a, b.
convert_file(to, from)- Find the in-browser converter (if any) that turns one format into another, e.g. from='fbx' to='glb'. Returns the tool URL and notes, all client-side (files never upload). Use for 'how do I convert X to Y'. Required: from, to.
get_company(slug)- Profile of a frontier company: what they build, why it matters for frontier design, competitors and technologies from the knowledge graph. Required: slug.
get_definition(slug, family)- Get the definition and reference copy for a dictionary term, technology, sensor, or file format by slug (use `search` to find slugs). Required: family, slug.
identify_format(file)- Identify a file format from an extension, filename, or slug (e.g. 'step', 'scan.mcap', 'gltf') and get how to open or convert it: what it stores, its extensions/MIME/spec, whether a free in-browser viewer exists, and available client-side conversions. Use for 'what is this file' / 'how do I open X'. Required: file.
list_design_jobs(limit, industry)- Latest design/UX/HMI roles at frontier companies (defense, robotics, space, industrial, health), refreshed from company job boards.
search(query)- Full-text search across Falcon's frontier design reference: terms, technologies, file formats, sensors, companies, tools, standards. Required: query.
Last successful function declaration observed on . Source: https://falcon.so/api/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://falcon.so/api/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-08-06 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-08-06 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 7 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | falcon.so | |
| mcp endpoint status | ok | The server listed 7 functions when asked. | as of probe | falcon.so |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json