Nordax AI Entity Network
REMOTE · MCP.NORDAX.AI · SCANNED AUG 3
Search and verify 360K+ business entities with trust scores and W3C credentials.
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 →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation 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. See how to fix → View diagnostics → Unverified
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- 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 Usability45
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.nordax.ai
claude mcp add --transport http ai-nordax-mcp https://mcp.nordax.ai/mcp
[mcp_servers.ai-nordax-mcp] url = "https://mcp.nordax.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-nordax-mcp": {
"type": "remote",
"url": "https://mcp.nordax.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-nordax-mcp --url https://mcp.nordax.ai/mcp --transport streamable-http
mcp_servers:
ai-nordax-mcp:
url: "https://mcp.nordax.ai/mcp" {
"mcpServers": {
"ai-nordax-mcp": {
"type": "http",
"url": "https://mcp.nordax.ai/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.
- 2 Aug 26 +6
- Schema quality: unverified → good ▲ functional
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 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
- 30 Jul 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
- 29 Jul 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.
- 28 Jul 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.
- 27 Jul 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
- 26 Jul 26 46
First indexed and scored.
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 3 Aug 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=YE2,O=Let's Encrypt,C=US | 21 Jun 2026 | 19 Sept 2026 | ECDSA 256 | ECDSA-SHA384 | 531afae0f816ad33e809a6d96703f1dbae9 |
| SANs: *.nordax.ai, nordax.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 |
DNSSEC insecure
Validation of mcp.nordax.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| nordax.ai. | 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 |
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 |
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.
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sign | boolean | — | Whether to include cryptographic signature (default: true for Verified+) |
| slug | string | yes | Entity 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.
| Name | Type | Req | Description |
|---|---|---|---|
| authId | string | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Entity 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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The 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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Entity 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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Entity 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.
| Name | Type | Req | Description |
|---|---|---|---|
| actions | array | yes | Permitted actions (e.g. ['read', 'recommend', 'transact', 'purchase', 'book']) |
| agentId | string | yes | DID of the agent being authorized (e.g. 'did:web:agent.example.com') |
| agentType | string | yes | Type of agent |
| entityId | string | — | Optional entity ID to scope the authorization to a specific business |
| principalIdentity | string | yes | Identity of the authorizing human (email, user ID) — will be SHA-256 hashed, never stored raw |
| validityDays | number | — | Custom validity period in days (overrides verification level default, max 365) |
| verificationLevel | string | yes | Verification 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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | — | City to filter by |
| entity_type | string | yes | Entity type to filter by. Options: LocalBusiness, Organization, ProfessionalService, Restaurant, MedicalBusiness, LegalService, FinancialService, EducationalOrganization, HomeAndConstructionBusiness,… |
| limit | number | — | Max results (default 20) |
| state | string | — | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | — | City name |
| name | string | — | Business name (partial or full) |
| phone | string | — | Business phone number |
| query | string | — | Free-text search query |
| state | string | — | US state abbreviation |
| url | string | — | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max results (default 10) |
| location | string | — | Location filter (e.g. 'Austin, TX' or 'Nashville') |
| query | string | yes | Search 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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | — | Filter by city name |
| entity_type | string | — | Filter by entity type. Options: LocalBusiness, Organization, ProfessionalService, Restaurant, MedicalBusiness, LegalService, FinancialService, EducationalOrganization, HomeAndConstructionBusiness, Au… |
| limit | number | — | Max results to return (default 10, max 50) |
| query | string | — | Free-text search query (e.g. 'dentist', 'acme plumbing') |
| state | string | — | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentIdentifier | string | — | Identifier for the AI agent submitting feedback |
| confidence | number | — | Confidence level from 0 to 1 |
| entitySlug | string | yes | Entity slug the feedback is about |
| interactionType | string | yes | Type of interaction, e.g. 'recommendation', 'verification', 'contact' |
| notes | string | — | Optional free-text notes about the interaction |
| outcome | string | yes | Outcome 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.
| Name | Type | Req | Description |
|---|---|---|---|
| credential | string | yes | The full HAP credential as a JSON string |
No output schema declared.
No examples provided.