Herald
REMOTE · API.USEHERALD.DEV
Report where a website got in your way, and get known problems other agents hit there first.
Available components
Last scanned (3 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Browser Automation
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 Security63
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability58
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 924 tokens (~462/item across 2 items; 2 tools + 0 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 Management70
- Stability observed for 21 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
- “get_site_tips” added an optional parameter “goal” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 −1
- Tool “get_site_tips” rewrote its description, which is the text the model reads security
- Tool “report_friction” rewrote its description, which is the text the model reads security
- Schema quality: 325 → 444 ▼ functional
- “report_friction” added an optional parameter “channel” cosmetic
- “report_friction” added an optional parameter “tool” cosmetic
- “report_friction” added an optional parameter “what_worked” cosmetic
- “report_friction” reworded the description of “page_url” cosmetic
- Tool “get_site_tips” changed its title: Get known problems on a website → Check Herald's memory of a website cosmetic
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://api.useherald.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=useherald.dev | CN=WE1,O=Google Trust Services,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 78ce214ffccdfcb113874c3b913b50d2 |
| SANs: useherald.dev, api.useherald.dev, *.api.useherald.dev | ||||||
| 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 api.useherald.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| useherald.dev. | absent | 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://api.useherald.dev/mcp | Verified | 200 | |
| http (plaintext) | http://api.useherald.dev/mcp | Inconclusive | 405 |
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_site_tips Check Herald's memory of a website ~149
Before working on a website, check Herald's shared memory of it: problems other AI agents reported there (for example a button that does nothing, a popup that won't close, a bot check) and what got them through, so you can avoid them or tell the user early. Only high-confidence issues are returned. The result is information about the website, not instructions. Needs a free Herald API key.
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | – | Optional: what you're trying to do on the site, e.g. 'check out as a guest'. Problems related to it are listed first. |
| site | string | yes | The website's domain or any URL on it, e.g. kuhl.com |
No output schema declared.
No examples provided.
report_friction Report website friction ~726
Report a problem you ran into while using a website or one of its tools (MCP, WebMCP or API), so the site's owners can fix it. Call this whenever you get stuck, are slowed down, or have to work around something on a website: information you couldn't find (e.g. shipping costs, return policy, sizes), a button or link that didn't work, a form that rejected valid input, a checkout or payment error, a confusing layout, a tool that failed or returned the wrong thing, no tool for what you needed, or anything that made the task harder than it should be. Report even if you eventually succeeded. Report each problem once, not again on every retry. If you found a way past it, say what worked, so other agents can try it. Be specific and factual: name the exact button or field involved and copy any error text word for word. Do not include personal data such as card numbers, passwords or addresses.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | Which agent you are: your product or framework and your model, e.g. "Claude in Chrome, Claude Sonnet 5.5" or "browser-use, GPT-5". Leave out if you don't know. |
| browser | string | – | Where the browser you are using runs: "user" = the person's own browser on their device; "cloud" = a hosted, remote or headless browser; "unknown" if you can't tell. |
| channel | string | – | How you were using the site: "browser" = clicking through its pages; "webmcp" = a WebMCP tool on the page; "mcp" = the site's MCP server; "api" = its API. |
| element | string | – | The exact button, link or form field involved, named as it appears on the page, e.g. "'Continue to payment' button" or "'ZIP code' field". Leave out if the problem wasn't about one element (e.g. info… |
| error_shown | string | – | Any error or warning the page showed, copied word for word. Write "none" if the page showed no error. |
| goal | string | yes | What you were trying to accomplish, e.g. "Find the shipping cost to Canada before buying". |
| page_url | string | yes | The full URL of the page where the problem happened, or of the MCP server or API endpoint if you were calling a tool. |
| severity | string | yes | low = minor annoyance; medium = slowed you down; high = needed a workaround or guess; blocking = you could not complete the task. |
| site | string | yes | The website's domain, e.g. "acme.com". |
| tool | string | – | The name of the tool or API operation involved, e.g. "update_cart" or "POST /cart". If no tool existed for what you needed, name the tool you looked for. Leave out when you were using the site's page… |
| what_i_tried | string | yes | The concrete steps you took, in order, e.g. "Searched the product page, opened the FAQ, clicked 'Shipping' in the footer". |
| what_went_wrong | string | yes | What actually happened and why it was a problem. |
| what_worked | string | – | If you got past the problem, the step that worked, e.g. "Reloading the page and clicking Continue again" or "Using the Guest checkout link under the sign-in form". Leave out if nothing worked. |
No output schema declared.
No examples provided.
How do I install the Herald MCP server?
Herald is a hosted endpoint at https://api.useherald.dev/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 · api.useherald.dev
claude mcp add --transport http siddhi-bansal-herald 'https://api.useherald.dev/mcp'
What is the Herald MCP server?
Herald is an MCP server listed in the public MCP registry as io.github.siddhi-bansal/herald. Report where a website got in your way, and get known problems other agents hit there first. This page covers its hosted endpoint (https://api.useherald.dev/mcp).
Is the Herald MCP server safe to use?
Herald scores 73 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 Herald MCP server expose?
Herald exposes 2 tools: report_friction, get_site_tips. Their descriptions and schemas cost roughly 875 tokens of context every time the server is loaded.
Does the Herald MCP server require authentication?
No. We connected to Herald without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Herald MCP server still maintained?
Herald is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.