MESSORA
REMOTE · MCP.MESSORA.DEV · SCANNED SEP 22
Scrape, crawl and search the web for AI agents via MCP.
Available components
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 Security74
- 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 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 Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 503 tokens (~100/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the MESSORA MCP server?
MESSORA is a hosted endpoint at https://mcp.messora.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 · mcp.messora.dev
claude mcp add --transport http dev-messora-messora 'https://mcp.messora.dev/mcp'
{
"mcpServers": {
"dev-messora-messora": {
"url": "https://mcp.messora.dev/mcp"
}
}
} {
"servers": {
"dev-messora-messora": {
"type": "http",
"url": "https://mcp.messora.dev/mcp"
}
}
} [mcp_servers.dev-messora-messora] url = "https://mcp.messora.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-messora-messora": {
"type": "remote",
"url": "https://mcp.messora.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-messora-messora --url 'https://mcp.messora.dev/mcp' --transport streamable-http
mcp_servers:
dev-messora-messora:
url: "https://mcp.messora.dev/mcp" {
"McpServers": {
"dev-messora-messora": {
"Transport": "http",
"Url": "https://mcp.messora.dev/mcp"
}
}
} assistant mcp add dev-messora-messora -t streamable-http -u 'https://mcp.messora.dev/mcp'
{
"mcpServers": {
"dev-messora-messora": {
"type": "http",
"url": "https://mcp.messora.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 11 Sept 26 0
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Sept 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.
- 30 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 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 22 Sept 2026 · Probed https://mcp.messora.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.messora.dev | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5154f6f04ea1baaa1e44978deec5dedb732 |
| SANs: mcp.messora.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.messora.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| messora.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://mcp.messora.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.messora.dev/mcp | HTTPS enforced | 301 | https://mcp.messora.dev/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_job ~50
Get the status and result of a crawl or search job. Terminal states: SUCCESS, FAILURE and REVOKED; PENDING/STARTED must be polled again.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_usage ~24
Get the plan, credits used and remaining balance of the MESSORA account.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
scrape_url ~168
Extract content starting from a URL. Synchronous: returns the content directly, no job_id. Follows up to max_pages pages from that URL (default 1). Consumes credit only when the backend returns scrape_status=success.
| Name | Type | Req | Description |
|---|---|---|---|
| fact_check | boolean | – | – |
| follow_subdomains | boolean | – | – |
| formats | array | – | – |
| include_frames | boolean | – | – |
| json_prompt | – | – | – |
| json_schema | – | – | – |
| max_age_ms | – | – | – |
| max_depth | – | – | – |
| max_pages | integer | – | – |
| only_main_content | boolean | – | – |
| parse_pdf | boolean | – | – |
| render_js | boolean | – | – |
| tags | – | – | – |
| timeout | – | – | – |
| url | string | yes | – |
| wait_for | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
start_crawl ~167
Start an asynchronous crawl and return a job_id. Poll get_job until PENDING/STARTED becomes SUCCESS, FAILURE or REVOKED.
| Name | Type | Req | Description |
|---|---|---|---|
| follow_subdomains | boolean | – | – |
| include_frames | boolean | – | – |
| include_images | boolean | – | – |
| include_links | boolean | – | – |
| max_depth | – | – | – |
| max_pages | integer | yes | – |
| only_main_content | boolean | – | – |
| parse_pdf | boolean | – | – |
| pdf_ocr | boolean | – | – |
| settle_animations | boolean | – | – |
| shorten_base64 | boolean | – | – |
| tags | array | – | – |
| timeout_ms | integer | – | – |
| url | string | yes | – |
| url_regex | string | – | – |
| wait_for_ms | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
start_search ~94
Start an asynchronous premium web search and return a job_id. Poll get_job until a terminal state.
| Name | Type | Req | Description |
|---|---|---|---|
| country | – | – | – |
| exclude_domains | – | – | – |
| freshness | – | – | – |
| include_domains | – | – | – |
| num_results | integer | – | – |
| query | string | yes | – |
| query_fanout | boolean | – | – |
| tags | – | – | – |
| timeout_seconds | – | – | – |
| use_cache | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the MESSORA MCP server?
MESSORA is an MCP server listed in the public MCP registry as dev.messora/messora. Scrape, crawl and search the web for AI agents via MCP. This page covers its hosted endpoint (https://mcp.messora.dev/mcp).
Is the MESSORA MCP server safe to use?
MESSORA scores 80 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 MESSORA MCP server expose?
MESSORA exposes 5 tools: scrape_url, start_crawl, start_search, get_job, get_usage. Their descriptions and schemas cost roughly 503 tokens of context every time the server is loaded.
Does the MESSORA MCP server require authentication?
No. We connected to MESSORA without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MESSORA MCP server still maintained?
MESSORA is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.