Frontier Desk
REMOTE · WWW.FRONTIERDESK.AI
Read Frontier Desk's AI-data buyer index, notes, markets and guides. Read-only, no key.
Available components
Last scanned (21 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3265 tokens (~155/item across 21 items; 17 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 0
- “get_outlook” reworded the description of “outlook” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 12 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 11 Nov 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://www.frontierdesk.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.frontierdesk.ai | CN=YR1,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | RSA 2048 | SHA256-RSA | 625903366b4076c18147abd15c3be0840ab |
| SANs: www.frontierdesk.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.frontierdesk.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| frontierdesk.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | default-src 'self'; script-src 'self' 'nonce-ZDY5ODRhYzEtYzVjMy00MTYxLWE3NTItNjVjYWQyMjg1MGFm' https://www.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com https://accounts.google.com https://challenges.cloudflare.com https://vercel.live https://va.vercel-scripts.com https://vitals.vercel-insights.com; style-src 'self' 'unsafe-inline' https://api.fontshare.com https://vercel.live; img-src 'self' data: blob: https://www.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com https://www.google.com https://stats.g.doubleclick.net https://vercel.live https://vercel.com; font-src 'self' data: https://cdn.fontshare.com https://vercel.live https://assets.vercel.com; connect-src 'self' data: https://www.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com https://www.google.com https://stats.g.doubleclick.net https://accounts.google.com https://challenges.cloudflare.com https://api.fontshare.com https://cdn.fontshare.com https |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.frontierdesk.ai/mcp | Verified | 200 | |
| http (plaintext) | http://www.frontierdesk.ai/mcp | HTTPS enforced | 308 | https://www.frontierdesk.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_guide Read one guide ~64
One guide in full: its quick answer, its text as markdown, the day it was last updated, and its address on the site. Takes a slug from list_guides.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The guide's slug, for example "sell-an-msp". |
No output schema declared.
No examples provided.
get_market_sector One sector's relationship graphs ~320
One sector's relationship graphs: the firms drawn in each column, the relations between them in each side's own words, the roster of who does what, and the lines on what the connections show. Takes a sector slug from list_markets: accounting, insurance, wealth, it, healthcare, staffing, legal, engineering, marketing, logistics, distribution, operators, software, business-services, property, manufacturing, build-out. By default (detail "summary") it answers compactly: per graph, the counts, the columns, the lines on what the connections show, and the first firms and relations in the order the page draws them, each named, with a link to the full JSON. detail "full" answers with the same JSON the /markets page loads when a visitor picks that sector, which can run past 100 KB.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | "summary" (the default) for counts and the first firms and relations in each graph; "full" for the whole JSON the page loads. |
| graph | string | – | One graph instead of all of them, by key, for example "services" or "credit". Omit for every graph the sector has. |
| limit | integer | – | With detail "summary": how many firms and relations to name per graph. Default 12. |
| sector | string | yes | The sector to draw: accounting, insurance, wealth, it, healthcare, staffing, legal, engineering, marketing, logistics, distribution, operators, software, business-services, property, manufacturing, b… |
No output schema declared.
No examples provided.
get_note Read one published note ~100
One published note in full: its text as written, the day it was published, its address on the site, and every link it cites. Takes the slug from list_notes or search_notes, or the last part of a note's own URL.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The note's slug, for example "2026-10-28-a-note-title-1a2b3c4d". A full /intel/... path works too. |
No output schema declared.
No examples provided.
get_outlook Read one outlook's odds and readings ~226
One standing forecast: the odds Frontier Desk gives every path at each of the two dates it is scored on, the readings behind them, the scenarios with the markers that say which one we are on, and when it is next rescored. Odds come from a simulation of chained steps and are the desk's own; they are not a market price and nothing settles them but the dated public sources each report names. The whole report is on its page.
| Name | Type | Req | Description |
|---|---|---|---|
| outlook | string | yes | The outlook's route, as list_outlooks gives it: /outlook/company-data-market-2027, /outlook/ai-jobs-and-income-2035, /outlook/compute-financing-2028, /outlook/data-center-power-2028, /outlook/private… |
No output schema declared.
No examples provided.
get_public_page Read one public page's framing ~168
One public page as written: its heading, its lead, and the sections it carries — what the page says it does, what it covers, and what it does not. This returns copy, not a run: the tools on these pages compute from a reader's own answers, and nothing here invents one. Routes: /tools, /first-pass, /deal-ready-ai, /roadmap, /data, /second-opinion, /compute, /build, /agents, /tools/mcp.
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | yes | The page's route, as list_public_pages gives it: /tools, /first-pass, /deal-ready-ai, /roadmap, /data, /second-opinion, /compute, /build, /agents, /tools/mcp. |
No output schema declared.
No examples provided.
get_vertical Read one services vertical ~117
One services vertical in full: the example firm it illustrates (headcount band, the tools such a firm runs on, how far its records go back, and the routes worth weighing), what changes in that line of work, and what decides whether a firm in it may license at all. The card is an illustration and says so in `evidence`. Figures for a real company come from instant_range, which quotes each buyer program's own published page.
| Name | Type | Req | Description |
|---|---|---|---|
| vertical | string | yes | The vertical's key, as list_verticals gives it. |
No output schema declared.
No examples provided.
instant_range Published range for a company ~281
The span of published per-company figures across the buyer programs a company of this size and age clears, with every source named and quoted. Give headcount and years if you know them; a company that has not stated one is not screened on it. A program is dropped only when the company certainly cannot meet its own stated floor. A /data band is screened the way /data screens it, at the top of the band, so a program is dropped only when the whole band is below its floor; the answer echoes the band, the figure it was screened as, and the programs that depend on where in the band the company sits. Returns has_range: false, with a reason, when fewer than two programs qualify — one program's advertisement is not a range, and no figure is estimated to fill the gap.
| Name | Type | Req | Description |
|---|---|---|---|
| headcount | integer | – | Full-time employees. Omit if unknown. |
| headcount_band | string | – | A /data headcount band instead of an exact figure: 1_29, 30_99, 100_249, 250_plus. |
| years | integer | – | Years of records the company holds. Omit if unknown. |
| years_band | string | – | A /data years band instead of an exact figure: under_3, 3_5, 6_10, 11_plus. |
No output schema declared.
No examples provided.
list_guides List the desk's guides ~123
Frontier Desk's guides: one page per question an owner asks before a sale, a loan or a data licence. Each row carries the question the guide answers, a forty-to-sixty-word answer to it, the day the guide was last updated, and its address. Pass a slug from here to get_guide for the whole guide. Newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many guides to return. |
| query | string | – | Words to find in a guide's title, question or description, for example "MSP" or "data room". |
No output schema declared.
No examples provided.
list_markets List the five markets ~87
The five markets Frontier Desk maps — services, compute, data, credit and capital — with the relationship graphs drawn in each, the columns each graph runs through, the sectors a caller can pick, and counts of what is drawn. Pass a sector slug from here to get_market_sector for that sector's graphs. The whole-field graphs render at https://www.frontierdesk.ai/markets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_notes List the desk's published notes ~129
Frontier Desk's published notes, newest first: each one's title, the day it was published, its own address on the site, and its first sentence. Pass a slug from here to get_note for the whole note. The same notes render at https://www.frontierdesk.ai/intel, with an RSS feed at https://www.frontierdesk.ai/intel/rss.xml.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many notes to return, newest first. |
| since | string | – | Only notes published on or after this day, as YYYY-MM-DD. For example "2026-10-01". |
No output schema declared.
No examples provided.
list_outlooks List the standing outlooks ~55
Frontier Desk's standing forecasts: what each one forecasts and over what horizon, the day it was published, and the date it is next rescored. Pass a route from here to get_outlook for the odds on every path.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_public_pages List the desk's public tool pages ~108
The tools Frontier Desk publishes for owners, each with what a reader gets from running it, plus the written pages behind them. Pass a route from here to get_public_page for that page's framing as written. The hub renders at https://www.frontierdesk.ai/tools. Every tool on this page runs on what you already know about the company and answers in one sitting. None of them asks for a data room, and none of them is a form that goes somewhere to be read later.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_verticals List the services verticals ~85
The services verticals Frontier Desk writes a page for: what a data licence looks like in that line of work, the shape of firm each page illustrates, and what decides whether a firm in it may license at all. Pass a key from here to get_vertical. Each page's example card is an illustration, labelled as one; no dollar figure is ever stored on a vertical.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_firm Look up a firm in the markets directory ~131
A firm in Frontier Desk's markets directory, by name: what kind of firm it is in plain words, its own site, the relationships held for it (what it bought, backed, lent to or borrowed from, each naming the other party), and a line on its recent activity. Up to eight firms per call. This is the public projection: no internal ids, codes, tags, evidence text or third-party scores cross it, and no client, mandate or engagement is reachable here.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Part of a firm's name, for example "Monroe" or "CORE Industrial". |
No output schema declared.
No examples provided.
read_data_offer Read a data-licensing offer ~172
Reads a pasted data-licensing offer and returns what it finds, with the offer's own words quoted back: the figure set against the published span, the payment trigger, exclusivity, export method and data retention — each reported as stated or as not stated — plus the terms worth settling before signing and the question to ask on each. A term the offer is silent on is reported as a finding, not filled in. Nothing is stored, and this is not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| headcount | integer | – | Full-time employees, so the price is set against the programs this company clears. Omit if unknown. |
| offer | string | yes | The offer text: a term sheet, an email, or the part to be read. |
| years | integer | – | Years of records. Omit if unknown. |
No output schema declared.
No examples provided.
search_data_buyers Search the AI-data buyer index ~192
Frontier Desk's dated index of AI-data buyer programs, one row per program: what it buys, the per-company figures and size screens it publishes, its stated payment trigger, exclusivity, de-identification and export method, a verbatim quote from its own page, and the day that page was read. Filter by a word in the program's name or in what it buys, or narrow to the programs that publish a per-company figure. The same rows render at https://www.frontierdesk.ai/data-buyers, with .csv and .json twins.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many rows to return. |
| publishes_a_range | boolean | – | true for only the programs that publish a per-company dollar figure; false for only those that do not. |
| query | string | – | Words to find in a program name or in what it buys, for example "tickets" or "Handshake". |
No output schema declared.
No examples provided.
search_notes Search the desk's published notes ~118
The published notes that carry every word asked for, in their title or their text, newest first. Matching is literal and case-insensitive: nothing is stemmed, ranked or inferred, so an empty answer means the words are not in the corpus rather than that the desk has no view. Pass a slug from here to get_note for the whole note.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many notes to return. |
| query | string | yes | Words every matching note has to carry, for example "carve-out" or "data centre power". |
No output schema declared.
No examples provided.
How do I install the Frontier Desk MCP server?
Frontier Desk is a hosted endpoint at https://www.frontierdesk.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.frontierdesk.ai
claude mcp add --transport http ai-frontierdesk-desk 'https://www.frontierdesk.ai/mcp'
What is the Frontier Desk MCP server?
Frontier Desk is an MCP server listed in the public MCP registry as ai.frontierdesk/desk. Read Frontier Desk's AI-data buyer index, notes, markets and guides. Read-only, no key. This page covers its hosted endpoint (https://www.frontierdesk.ai/mcp).
Is the Frontier Desk MCP server safe to use?
Frontier Desk scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Frontier Desk MCP server expose?
Frontier Desk exposes 17 tools: search_data_buyers, instant_range, read_data_offer, list_notes, search_notes, and 12 more. Their descriptions and schemas cost roughly 2,476 tokens of context every time the server is loaded.
Does the Frontier Desk MCP server require authentication?
No. We connected to Frontier Desk without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Frontier Desk MCP server still maintained?
Frontier Desk is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Frontier Desk MCP server?
VerifyMCP ran 13 checks on Frontier Desk, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.