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.

Agent Master Data

REMOTE · API.AGENTMASTERDATA.COM

Paid x402 API and MCP for trusted public master data, golden records, and reference data.

78 Trust /100

Last scanned (9 hours ago)

Scores higher than 73% of remote servers

Reachable. Last reached 6 Nov 2026.

Category Data and Analytics

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 Security83
  • 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1384 tokens (~138/item across 10 items; 7 tools + 3 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 Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 86% 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
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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.

  • 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 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
    • Tool “search_master_data” changed its title: Search Trusted Master Data → Search Agent Master Data cosmetic
  • 31 Oct 26 75

    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 6 Nov 2026 · Probed https://api.agentmasterdata.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agentmasterdata.com CN=WE1,O=Google Trust Services,C=US 26 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA256 98afac18f4980e7c13b1e58a47e654f2
SANs: agentmasterdata.com, api.agentmasterdata.com, *.api.agentmasterdata.com
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 secure

Validation of api.agentmasterdata.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
agentmasterdata.com. DS published 2371 13 Verified
api.agentmasterdata.com. Verified address RRset verified with the apex keys
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=3600
content-security-policy default-src 'none'; base-uri 'none'; form-action 'none'; frame-ancestors 'none'
x-content-type-options nosniff
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://api.agentmasterdata.com/mcp Verified 200
http (plaintext) http://api.agentmasterdata.com/mcp HTTPS enforced 301 https://api.agentmasterdata.com/mcp
MCP tools · 7 exposed · ~1,198 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
assess_master_data_quality ~197

Paid x402 tool. Assess the completeness, validity, consistency, uniqueness, and freshness of a master-data record or supplied attributes. Returns explainable issues, severity, affected fields, policy rules, and safe remediation guidance without changing data. Price ID: price.quality.v1.

NameTypeReqDescription
attributesobject–Candidate attributes to assess without writing them. Supply this or record_id, never both. No value submitted here is stored, published, or echoed: the answer names the input by its digest alone.
dimensionsarray–The quality dimensions to assess. A registered rule scoring a dimension not asked for is absent from the answer's issues, passed_rules, and not_evaluated_rules alike.
entity_type–yes–
include_remediation_guidanceboolean–Whether each reported issue carries remediation guidance.
record_idstring–Existing golden-record ID to assess. Supply this or attributes, never both.

No output schema declared.

No examples provided.

get_master_data_golden_record ~80

Paid x402 tool. Retrieve one authoritative public golden record by stable record ID. Returns public attributes, identifiers, source-record lineage, survivorship evidence, freshness, relationships summary, and data quality. Price ID: price.record.v1.

NameTypeReqDescription
entity_type–yes–
record_idstringyesGolden-record identifier within the entity domain.

No output schema declared.

No examples provided.

get_master_data_relationships ~124

Paid x402 tool. Get governed public relationships for one master-data golden record, such as supplier ownership, location hierarchy, or organization parentage. Returns direction, validity dates, provenance, and confidence. Price IDs by requested depth: price.relationships.depth-1.v1, price.relationships.depth-2.v1, or price.relationships.depth-3.v1.

NameTypeReqDescription
depthinteger–Traversal depth. Each depth is a separately priced tier.
entity_type–yes–
record_idstringyesGolden-record identifier within the entity domain.

No output schema declared.

No examples provided.

get_master_data_schema ~144

Free discovery tool. Get supported public master-data entity types, identifiers, searchable attributes, relationships, reference domains, coverage, and freshness. Use this first when an agent does not know the data model or valid filters.

NameTypeReqDescription
entity_type––Describe only this entity domain. Omitted means all v1 entity domains.
include_attributesboolean–When false, the attributes member is omitted from each described entity type.
include_identifiersboolean–When false, the identifiers member is omitted from each described entity type. primary_identifier is always present.
include_relationshipsboolean–When false, the relationships member is omitted from each described entity type.

No output schema declared.

No examples provided.

get_reference_data ~419

Paid x402 tool. Get governed public reference data and controlled vocabulary values such as country, currency, unit of measure, industry, status, category, or code mappings. Returns codes, labels, definitions, validity dates, mappings, provenance, and version. Price ID: price.reference.v1.

NameTypeReqDescription
codesarray–Exact codes wanted. Set membership, never a substring match; omit it to narrow nothing.
cursorstring–Opaque continuation cursor from a prior identical request. Bound to the operation, the normalized request, and the data_version it paged.
domainstringyesReference-data domain identifier, as get_master_data_schema names it.
include_inactiveboolean–Whether values not KNOWN to be active at valid_at are served. False excludes them; true serves them flagged - active: false for a value declared inactive, beside the reference_value_inactive warning,…
limitinteger–Page size, applied after query, codes, and validity have narrowed the list.
localestring–Language tag echoed on every served value and in the answer. Labels are served exactly as the snapshot stores them; there is no translation layer.
querystring–Optional code or label search: a case-insensitive substring match against a value's code OR its label. Omit it to match every value.
valid_atstring–The instant to evaluate each value's validity interval at. Defaults to the request clock. A value whose source DECLARES its interval is active when valid_from <= valid_at < valid_to, an absent or nul…

No output schema declared.

No examples provided.

resolve_master_data_entity ~99

Paid x402 tool. Match incomplete or conflicting public supplier, location, or organization attributes to trusted master-data candidates. Returns explainable match evidence and never silently chooses an ambiguous entity. Price ID: price.resolve.v1.

NameTypeReqDescription
attributesobject–Identifying attribute values keyed by field name, e.g. a name or an address line.
entity_type–yes–
identifiersarray–Known identifiers of the entity being resolved.

No output schema declared.

No examples provided.

search_master_data ~135

Paid x402 tool. Search trusted public master data for suppliers, locations, or organizations. Returns bounded golden-record summaries with match reasons, confidence, provenance, public-use status, freshness, and data-quality scores. Price ID: price.search.v1. Read masterdata://pricing before payment.

NameTypeReqDescription
cursorstring–Opaque pagination cursor from a previous response's meta.next_cursor.
entity_type––Restrict the search to one entity domain. Omitted means all v1 entity domains.
limitinteger–Maximum number of results per page.
querystringyesFree-text search over golden records.

No output schema declared.

No examples provided.

Install

How do I install the Agent Master Data MCP server?

Agent Master Data is a hosted endpoint at https://api.agentmasterdata.com/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.agentmasterdata.com

# add to Claude Code
claude mcp add --transport http com-agentmasterdata-agent-master-data 'https://api.agentmasterdata.com/mcp'
Common questions

What is the Agent Master Data MCP server?

Agent Master Data is an MCP server listed in the public MCP registry as com.agentmasterdata/agent-master-data. Paid x402 API and MCP for trusted public master data, golden records, and reference data. This page covers its hosted endpoint (https://api.agentmasterdata.com/mcp).

Is the Agent Master Data MCP server safe to use?

Agent Master Data scores 78 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 Agent Master Data MCP server expose?

Agent Master Data exposes 7 tools: get_master_data_schema, search_master_data, resolve_master_data_entity, get_master_data_golden_record, get_master_data_relationships, and 2 more. Their descriptions and schemas cost roughly 1,198 tokens of context every time the server is loaded.

Does the Agent Master Data MCP server require authentication?

No. We connected to Agent Master Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Agent Master Data MCP server still maintained?

Agent Master Data is still listed as active in the MCP registry. We last reached this channel on 6 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 Agent Master Data MCP server?

VerifyMCP ran 13 checks on Agent Master Data, 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.