Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

LocalMark Hosted Agents

REMOTE · AGENTS.LOCALMARK.AI

Documents, data, localization, A2A repair and x402 analysis. Shared trial, then 0.05 USDC/task.

+3 this week 72 Trust /100

Last scanned (16 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

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
Schema Quality & AI Usability44
  • AI-judged instruction clarity (poor).Fail
  • Context-footprint check failed: tool/resource definitions use about 700 tokens (~140/item across 5 items; 5 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 Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
What we tested

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 →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 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 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.

  • 13 Nov 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.

  • 11 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.

  • 9 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.

  • 7 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 6 Nov 26 65

    First indexed and scored.

Diagnostics

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://agents.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=agents.localmark.ai CN=YE2,O=Let's Encrypt,C=US 28 Oct 2026 26 Jan 2027 ECDSA 256 ECDSA-SHA384 6cd6bf26fa39268a9a4b399c836ddee7c6a
SANs: agents.localmark.ai
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 agents.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'; font-src 'self'; img-src 'self' https://localmark.ai 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 no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agents.localmark.ai/mcp Verified 200
http (plaintext) http://agents.localmark.ai/mcp HTTPS enforced 308 https://agents.localmark.ai/mcp
MCP tools · 5 exposed · ~431 tokens

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 →

Tool Tokens
advise_agentops ~86

Analyze a supplied Agent Card and optional previous card; explain local version-aware repair/diff checks using OpenAI. No live endpoint requests.

NameTypeReqDescription
allow_model_processingboolean––
force_new_taskboolean––
payloadobjectyes–
payment_signaturestring––
request_idstring––
skip_free_trialboolean––

No output schema declared.

No examples provided.

analyze_data ~85

Profile bounded CSV/JSON locally and ask OpenAI to explain computed facts. Requires explicit authorization; no generated code or external data sources.

NameTypeReqDescription
allow_model_processingboolean––
force_new_taskboolean––
payloadobjectyes–
payment_signaturestring––
request_idstring––
skip_free_trialboolean––

No output schema declared.

No examples provided.

analyze_document ~93

Analyze supplied text with checked quote references. No PDF/URL fetch. One free trial/network/30 days; then 0.05 USDC on Base via x402.

NameTypeReqDescription
allow_model_processingboolean––
force_new_taskboolean––
payloadobjectyes–
payment_signaturestring––
request_idstring––
skip_free_trialboolean––

No output schema declared.

No examples provided.

analyze_payment_offers ~85

Compare supplied x402 declarations with exact local amount calculations and OpenAI commentary. No paid endpoint calls, wallet actions or payment.

NameTypeReqDescription
allow_model_processingboolean––
force_new_taskboolean––
payloadobjectyes–
payment_signaturestring––
request_idstring––
skip_free_trialboolean––

No output schema declared.

No examples provided.

localize_content ~82

Translate supplied text or flat JSON strings using OpenAI, validating keys/placeholders. Explicit authorization and shared allowance required.

NameTypeReqDescription
allow_model_processingboolean––
force_new_taskboolean––
payloadobjectyes–
payment_signaturestring––
request_idstring––
skip_free_trialboolean––

No output schema declared.

No examples provided.

Install

How do I install the LocalMark Hosted Agents MCP server?

LocalMark Hosted Agents is a hosted endpoint at https://agents.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 · agents.localmark.ai

# add to Claude Code
claude mcp add --transport http ai-localmark-hosted-agents 'https://agents.localmark.ai/mcp'
Common questions

What is the LocalMark Hosted Agents MCP server?

LocalMark Hosted Agents is an MCP server listed in the public MCP registry as ai.localmark/hosted-agents. Documents, data, localization, A2A repair and x402 analysis. Shared trial, then 0.05 USDC/task. This page covers its hosted endpoint (https://agents.localmark.ai/mcp).

Is the LocalMark Hosted Agents MCP server safe to use?

LocalMark Hosted Agents scores 72 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 Hosted Agents MCP server expose?

LocalMark Hosted Agents exposes 5 tools: analyze_document, analyze_data, localize_content, advise_agentops, analyze_payment_offers. Their descriptions and schemas cost roughly 431 tokens of context every time the server is loaded.

Does the LocalMark Hosted Agents MCP server require authentication?

No. We connected to LocalMark Hosted Agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the LocalMark Hosted Agents MCP server still maintained?

LocalMark Hosted Agents 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 Hosted Agents MCP server?

VerifyMCP ran 13 checks on LocalMark Hosted Agents, 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.