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.

Nordax AI Entity Network

REMOTE · MCP.NORDAX.AI

Search and verify 360K+ business entities with trust scores and W3C credentials.

Available components

0 this week 69 Trust /100

Last scanned (16 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

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 Security46
Transport & Reachability100
Schema Quality & AI Usability49
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1563 tokens (~111/item across 14 items; 13 tools + 1 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 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 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
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Oct 26 +10
    • Transport: fail → pass ▲ security
  • 23 Oct 26 59
    • Transport: pass → fail ▼ security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://mcp.nordax.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=nordax.ai CN=YE1,O=Let's Encrypt,C=US 18 Oct 2026 16 Jan 2027 ECDSA 256 ECDSA-SHA384 6490527b81be32846bf1b3103a2c63acef1
SANs: *.nordax.ai, nordax.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 mcp.nordax.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
nordax.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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.nordax.ai/mcp Verified 200
http (plaintext) http://mcp.nordax.ai/mcp Inconclusive 405
MCP tools · 13 exposed · ~1,559 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
attest_entity ~130

Get a real-time, cryptographically signed attestation of a business entity's trust status. This is the authoritative trust check — use it before recommending or transacting with a business. Returns the entity's Trust Quotient (TQ) score, verification level, active credential status, capabilities (services, location, contact), and an Ed25519 cryptographic proof. Signed attestations are available for Verified tier and above.

NameTypeReqDescription
signboolean–Whether to include cryptographic signature (default: true for Verified+)
slugstringyesEntity slug to attest (from search results or known entity)

No output schema declared.

No examples provided.

check_authorization_status ~68

Check the real-time status of an HAP authorization credential. Returns whether the credential is active, expired, revoked, or suspended. Use this for lightweight status checks without submitting the full credential.

NameTypeReqDescription
authIdstringyesThe credential's authId (urn:uuid:... format)

No output schema declared.

No examples provided.

fetch ~94

Fetch detailed data about a specific Nordax AI entity by URL or slug. Returns the full entity profile including verification status, trust tier, contact info, services, AI visibility score, and llms.txt summary (if available). Use this after search to get complete entity details.

NameTypeReqDescription
urlstringyesEntity URL (e.g. 'https://nordax.ai/entities/acme-plumbing-abc123') or entity slug

No output schema declared.

No examples provided.

get_entity ~82

Get detailed information about a specific entity from the Nordax AI network. Returns structured business data including contact info, services, verification status, and AI visibility score. Use the entity slug (from search results) or entity name.

NameTypeReqDescription
slugstringyesThe entity slug (e.g. 'acme-plumbing-abc123') or entity name to look up

No output schema declared.

No examples provided.

get_entity_credential ~87

Retrieve the active W3C Verifiable Entity Credential (VEC) for a business. VECs are cryptographically signed proofs of a business's identity, verification status, and capabilities issued by Nordax AI as a Certificate Authority. Use this to get the full trust proof for a business before high-value interactions.

NameTypeReqDescription
slugstringyesEntity slug to get the credential for

No output schema declared.

No examples provided.

get_entity_verification ~79

Check the verification and trust status of an entity. Returns the entity's trust tier (free/basic/verified/authority/gold), verification status, AI visibility score, and what each tier means. Use this to verify the legitimacy of a business in the Nordax network.

NameTypeReqDescription
slugstringyesEntity slug or name to check verification for

No output schema declared.

No examples provided.

issue_hap_authorization ~237

Issue a Human Authorization Protocol (HAP) credential to authorize an AI agent to act on a human's behalf. Creates a W3C Verifiable Credential 2.0 with scoped permissions, time-bounded validity, and a DataIntegrityProof signature. Requires authentication — the authenticated user becomes the credential owner.

NameTypeReqDescription
actionsarrayyesPermitted actions (e.g. ['read', 'recommend', 'transact', 'purchase', 'book'])
agentIdstringyesDID of the agent being authorized (e.g. 'did:web:agent.example.com')
agentTypestringyesType of agent
entityIdstring–Optional entity ID to scope the authorization to a specific business
principalIdentitystringyesIdentity of the authorizing human (email, user ID) — will be SHA-256 hashed, never stored raw
validityDaysnumber–Custom validity period in days (overrides verification level default, max 365)
verificationLevelstringyesVerification level — basic (7d default), enhanced (30d), full (90d)

No output schema declared.

No examples provided.

list_entities_by_category ~145

List entities of a specific type/category in a location. Great for questions like 'What restaurants are in Nashville?' or 'Find dentists in Austin, TX'. Results are ranked by verification tier and AI visibility score.

NameTypeReqDescription
citystring–City to filter by
entity_typestringyesEntity type to filter by. Options: LocalBusiness, Organization, ProfessionalService, Restaurant, MedicalBusiness, LegalService, FinancialService, EducationalOrganization, HomeAndConstructionBusiness,…
limitnumber–Max results (default 20)
statestring–US state abbreviation (e.g. 'TX')

No output schema declared.

No examples provided.

resolve_entity ~127

Resolve an ambiguous business reference to a verified Nordax entity. Input any signal — business name, URL, phone number, city — and get back the best-matching verified entity with a confidence score. Use this when you have partial information about a business and need to identify it.

NameTypeReqDescription
citystring–City name
namestring–Business name (partial or full)
phonestring–Business phone number
querystring–Free-text search query
statestring–US state abbreviation
urlstring–Business website URL

No output schema declared.

No examples provided.

search ~106

Search the Nordax AI entity network. Returns verified, structured business entity data ranked by trust tier and AI visibility score. Supports free-text queries, category filtering (LocalBusiness, Restaurant, MedicalBusiness, etc.), and location filtering.

NameTypeReqDescription
limitnumber–Max results (default 10)
locationstring–Location filter (e.g. 'Austin, TX' or 'Nashville')
querystringyesSearch query — business name, category, or description

No output schema declared.

No examples provided.

search_entities ~177

Search the Nordax AI entity network for businesses. Returns verified, structured entity data. Use this to find businesses by name, category, or location. Results are ranked by trust tier and AI visibility score.

NameTypeReqDescription
citystring–Filter by city name
entity_typestring–Filter by entity type. Options: LocalBusiness, Organization, ProfessionalService, Restaurant, MedicalBusiness, LegalService, FinancialService, EducationalOrganization, HomeAndConstructionBusiness, Au…
limitnumber–Max results to return (default 10, max 50)
querystring–Free-text search query (e.g. 'dentist', 'acme plumbing')
statestring–Filter by US state (e.g. 'TX', 'CA', 'NY')

No output schema declared.

No examples provided.

submit_feedback ~150

Submit feedback about an interaction with a Nordax-listed entity. Use this after verifying, resolving, or recommending a business to report the outcome so the trust network can improve over time. Feedback helps Nordax AI calibrate trust scores and entity rankings.

NameTypeReqDescription
agentIdentifierstring–Identifier for the AI agent submitting feedback
confidencenumber–Confidence level from 0 to 1
entitySlugstringyesEntity slug the feedback is about
interactionTypestringyesType of interaction, e.g. 'recommendation', 'verification', 'contact'
notesstring–Optional free-text notes about the interaction
outcomestringyesOutcome of the interaction

No output schema declared.

No examples provided.

verify_hap_authorization ~77

Verify an HAP authorization credential. Checks the cryptographic signature, expiration, and real-time revocation status. Use this before honoring an agent's request to act on a human's behalf. Submit the full credential JSON and get back a verification result.

NameTypeReqDescription
credentialstringyesThe full HAP credential as a JSON string

No output schema declared.

No examples provided.

Install

How do I install the Nordax AI Entity Network MCP server?

Nordax AI Entity Network is a hosted endpoint at https://mcp.nordax.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 · mcp.nordax.ai

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

What is the Nordax AI Entity Network MCP server?

Nordax AI Entity Network is an MCP server listed in the public MCP registry as ai.nordax/mcp. Search and verify 360K+ business entities with trust scores and W3C credentials. This page covers its hosted endpoint (https://mcp.nordax.ai/mcp).

Is the Nordax AI Entity Network MCP server safe to use?

Nordax AI Entity Network scores 69 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 Nordax AI Entity Network MCP server expose?

Nordax AI Entity Network exposes 13 tools: search_entities, get_entity, list_entities_by_category, get_entity_verification, attest_entity, and 8 more. Their descriptions and schemas cost roughly 1,559 tokens of context every time the server is loaded.

Does the Nordax AI Entity Network MCP server require authentication?

No. We connected to Nordax AI Entity Network without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Nordax AI Entity Network MCP server still maintained?

Nordax AI Entity Network 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 Nordax AI Entity Network MCP server?

VerifyMCP ran 11 checks on Nordax AI Entity Network, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Nordax AI Entity Network: Authorization and HTTPS. 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.