LocalMark Agent Directory
REMOTE · LOCALMARK.AI
Search public A2A agents and inspect read-only Agent Card and endpoint checks.
Available components
Last scanned (14 hours ago)
Scores higher than 83% of remote servers
Reachable. Last reached 21 Nov 2026.
Category AI and Machine Learning
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 Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 732 tokens (~122/item across 6 items; 6 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 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.
- 31 Oct 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.
- 29 Oct 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.
- 27 Oct 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.
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://localmark.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=localmark.ai | CN=YE1,O=Let's Encrypt,C=US | 7 Oct 2026 | 5 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 60e1514d5ce3de19d9d4ecba72503e9ccf9 |
| SANs: localmark.ai | ||||||
| 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 localmark.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| localmark.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=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; font-src 'self'; img-src 'self' data:; connect-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://localmark.ai/mcp | Verified | 200 | |
| http (plaintext) | http://localmark.ai/mcp | HTTPS enforced | 308 | https://localmark.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_agent ~48
Get a full public agent record by LocalMark ID, including original card and complete stored evidence. Collection previews are compact; this explicit detail tool is not truncated.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | integer | yes | – |
No output schema declared.
No examples provided.
get_connection_plan ~102
Read connection metadata for a public agent without connecting to it. Accepts a LocalMark agent ID, Agent Card URL, endpoint URL or domain. Returns advertised interfaces, authentication scheme metadata, input/output modes, skill names and stored evidence. A publisher domain may be ambiguous. The plan never includes credentials and never authorizes a task or payment. Obtain explicit task authorization before using any endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| target | string | yes | – |
No output schema declared.
No examples provided.
list_agents ~36
Browse public agents with pagination and repair_links to read-only publisher diagnostics.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
recommend_agents ~314
Recommend agents for a capability or job with matching reasons and caveats. Uses exactly the website/API ranking and stored observations, never a live task. Filters are requirements, so an empty shortlist is valid. auth is 'none' or 'declared'; signature is 'verified'; protocol is JSONRPC, HTTP+JSON or GRPC. a2a_confirmed requires the latest current-endpoint read-only probe to confirm A2A; it does not prove task quality or safety. Observation age is 1..168 hours. max_amount is a non-negative amount in human-readable asset units (0.05 means 0.05 USDC for a USDC asset) and requires both network and asset with known decimals. No price conversion across assets is performed. Returns compact structured results (4 KiB per record), total_matches, pagination, ranking_version and evidence scope. Use full_record_url or get_agent for full stored details.
| Name | Type | Req | Description |
|---|---|---|---|
| a2a_confirmed | boolean | – | – |
| a2a_response_within_hours | – | – | – |
| asset | string | – | – |
| auth | string | – | – |
| checked_within_hours | – | – | – |
| limit | integer | – | – |
| max_amount | string | – | – |
| network | string | – | – |
| offset | integer | – | – |
| protocol | string | – | – |
| query | string | yes | – |
| signature | string | – | – |
| tls_reachable | – | – | – |
No output schema declared.
No examples provided.
search_agents ~50
Search public agent names, descriptions and skills. Returns profile/card URLs and repair_links to stored publisher diagnostics; no task or probe is run.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
verify_agent ~69
Read stored checks for a card URL, endpoint URL or publisher domain. Unseen targets return listing_status 'not_seen', including available lookalike-domain hints. Publisher domains may return multiple matches. No live request is made to the publisher.
| Name | Type | Req | Description |
|---|---|---|---|
| card_url | string | yes | – |
No output schema declared.
No examples provided.
How do I install the LocalMark Agent Directory MCP server?
LocalMark Agent Directory is a hosted endpoint at https://localmark.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 · localmark.ai
claude mcp add --transport http ai-localmark-agent-directory 'https://localmark.ai/mcp'
What is the LocalMark Agent Directory MCP server?
LocalMark Agent Directory is an MCP server listed in the public MCP registry as ai.localmark/agent-directory. Search public A2A agents and inspect read-only Agent Card and endpoint checks. This page covers its hosted endpoint (https://localmark.ai/mcp).
Is the LocalMark Agent Directory MCP server safe to use?
LocalMark Agent Directory scores 83 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 LocalMark Agent Directory MCP server expose?
LocalMark Agent Directory exposes 6 tools: search_agents, recommend_agents, get_connection_plan, list_agents, get_agent, verify_agent. Their descriptions and schemas cost roughly 619 tokens of context every time the server is loaded.
Does the LocalMark Agent Directory MCP server require authentication?
No. We connected to LocalMark Agent Directory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LocalMark Agent Directory MCP server still maintained?
LocalMark Agent Directory 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 LocalMark Agent Directory MCP server?
VerifyMCP ran 13 checks on LocalMark Agent Directory, 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.