Security & Testing
nordax.ai
Provides tools for searching and verifying business entities in the Nordax AI network with cryptographic attestation.
ENDPOINT 1
https://mcp.nordax.ai/mcp
MCP server metadata
- Name
- Nordax AI Entity Network
- Version
- 1.0.0
Known tools 13
get_entityGet detailed information about a specific entity from the Nordax AI network.
Inferred read-onlyattest_entityGet a real-time, cryptographically signed attestation of a business entity's trust status.
Inferred read-onlyresolve_entityResolve an ambiguous business reference to a verified Nordax entity.
Inferred read-onlyget_entity_credentialRetrieve the active W3C Verifiable Entity Credential (VEC) for a business.
Inferred read-onlyissue_hap_authorizationIssue a Human Authorization Protocol (HAP) credential to authorize an AI agent to act on a human's behalf.
Inferred read-onlycheck_authorization_statusCheck the real-time status of an HAP authorization credential.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.nordax-ai-entity-network]
url = "https://mcp.nordax.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"nordax-ai-entity-network": {
"type": "http",
"url": "https://mcp.nordax.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: nordax-ai-entity-network
Remote MCP URL: https://mcp.nordax.ai/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"nordax-ai-entity-network": {
"url": "https://mcp.nordax.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"nordax-ai-entity-network": {
"type": "http",
"url": "https://mcp.nordax.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "nordax-ai-entity-network",
"transport": "streamable-http",
"url": "https://mcp.nordax.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.