Hummingbird
REMOTE · DATUM.QUEST
A no-account public commons. Any actor, human or automated, can read it and leave an offer.
Available components
Last scanned (19 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 2026.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (withdraw_offer). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 800 tokens (~114/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “make_offer” rewrote its description, which is the text the model reads security
- Schema quality: 658 → 800 ▼ functional
- New tool “list_asks” functional
- “make_offer” reworded the description of “question_id” cosmetic
- 20 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “make_offer” rewrote its description, which is the text the model reads security
- Schema quality: 75 → 109 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- 19 Nov 26 63
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://datum.quest/offer/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=datum.quest | CN=WE1,O=Google Trust Services,C=US | 9 Nov 2026 | 7 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 97ebfcd30ffce1650eec4d6bd70847b6 |
| SANs: datum.quest | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of datum.quest. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| quest. | DS published | 19889, 50071 | 8, 8 | Verified |
| datum.quest. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://datum.quest/offer/mcp | Verified | 200 | |
| http (plaintext) | http://datum.quest/offer/mcp | HTTPS enforced | 301 | https://datum.quest/offer/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_record Get a public record ~31
Returns one published canonical record as JSON, by the id that list_records gives.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
list_asks List specific asks ~80
Lists the few sentences on datum.quest that Hummingbird currently wants corrected, clarified, challenged or filled in, each with its exact text, a SHA-256 of that text, and its page. To answer one, call make_offer with your answer as offer and the ask's id as question_id. Answering is optional; any offer is welcome.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_records List public records ~24
Lists Hummingbird's published canonical records with their ids, types and states.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
make_offer Leave an offer ~267
Leaves a temporary, non-canonical offer in Hummingbird's pilot buffer, with no account. Acceptance is not admission, publication, a vote, identity, reputation or governance standing. Offers are read for what they say; exact repeats are grouped, and volume is not a vote. Kept for 30 days (22 for an answer to a listed ask) while Hummingbird is being stood up, then cleared; withdrawing clears it at once. No name, account, IP address or user-agent is stored. Read by Hummingbird's steward and reviewers, who use AI assistants to help; offers are not used to train AI models, and if that ever changes it will be stated first and apply only to later offers. Never published by being accepted; https://datum.quest/heard reports each review in coarse counts and never quotes offers. Offer text is 1 to 4,000 characters. On success the result holds a private receipt, shown once: keep it private.
| Name | Type | Req | Description |
|---|---|---|---|
| offer | string | yes | Your idea, criticism, correction, question, or evidence about Hummingbird. |
| question_id | string | – | Optional: the id of the ask you are answering, from list_asks. |
| reference | string | – | Optional http or https URL that supports the offer. |
No output schema declared.
No examples provided.
offer_status Check an offer ~39
Returns the current state and expiry of an offer, using its private receipt.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | string | yes | The private one-time receipt returned by make_offer. |
No output schema declared.
No examples provided.
read_guide Read the Hummingbird guide ~42
Returns Hummingbird's machine-readable guide (llms.txt): what it is, its boundaries, the questions it most wants answered, and where everything public lives.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
withdraw_offer Withdraw an offer ~45
Withdraws an offer from the pilot buffer, using its private receipt. Its text and reference are cleared.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | string | yes | The private one-time receipt returned by make_offer. |
No output schema declared.
No examples provided.
How do I install the Hummingbird MCP server?
Hummingbird is a hosted endpoint at https://datum.quest/offer/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 · datum.quest
claude mcp add --transport http sunw0lf-hummingbird 'https://datum.quest/offer/mcp'
What is the Hummingbird MCP server?
Hummingbird is an MCP server listed in the public MCP registry as io.github.SunW0lf/hummingbird. A no-account public commons. Any actor, human or automated, can read it and leave an offer. This page covers its hosted endpoint (https://datum.quest/offer/mcp).
Is the Hummingbird MCP server safe to use?
Hummingbird scores 64 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 Hummingbird MCP server expose?
Hummingbird exposes 7 tools: read_guide, list_asks, list_records, get_record, make_offer, and 2 more. Their descriptions and schemas cost roughly 528 tokens of context every time the server is loaded.
Does the Hummingbird MCP server require authentication?
No. We connected to Hummingbird without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Hummingbird MCP server still maintained?
Hummingbird 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 Hummingbird MCP server?
VerifyMCP ran 13 checks on Hummingbird, 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.