← Registry

API Tools

agentaccess.dk

Searches a catalog of Danish digital infrastructure, APIs, MCP servers, datasets, and AI integration enablers with detailed specifications and setup guides.

WebMCP2 endpoints6 known toolsFirst detected October 18, 2026Last detected October 18, 2026

ENDPOINT 1

https://agentaccess.dk/mcp

No auth detected

MCP server metadata

Name
agentaccess-mcp
Version
1.0.0
Capabilities
tools
Server instructions

AgentAccess.dk MCP server. Query Danish public APIs, civic digital products, and AX enablers.

Known tools 5

search_danish_directory

Search the AgentAccess catalog of Danish digital infrastructure, APIs, MCP servers, datasets, and civic systems (e.g.

Inferred read-only
get_tool_details

Get full specifications, authentication requirements, access tier, official status, use cases, and technical notes for a specific Danish tool by its slug.

Inferred read-only
search_enablers

Search curated AI Access Enablers and developer tooling (MCP server builders, browser automation runtimes, web scrapers, sandboxes) designed to connect agents to Danish systems.

Inferred read-only
get_enabler_details

Get deep technical details, features, recipes, and setup quickstarts for an AI access enabler tool by slug.

Inferred read-only
get_harness_integration

Get harness integration guides and configuration pointers to connect Danish tools to AI agents and frameworks (e.g.

Inferred read-only

CONNECT 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.agentaccess-mcp]
url = "https://agentaccess.dk/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "agentaccess-mcp": {
      "type": "http",
      "url": "https://agentaccess.dk/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: agentaccess-mcp
Remote MCP URL: https://agentaccess.dk/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": {
    "agentaccess-mcp": {
      "url": "https://agentaccess.dk/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "agentaccess-mcp": {
      "type": "http",
      "url": "https://agentaccess.dk/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "agentaccess-mcp",
  "transport": "streamable-http",
  "url": "https://agentaccess.dk/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://agentaccess.dk

No auth detected

MCP server metadata

Name
WebMCP
Capabilities
declarative

Known tools 1

subscribe_newsletter

Email when new Danish APIs, MCP servers, or automation recipes are added. Unsubscribe anytime.

Potential side effects

CONNECT 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.webmcp]
url = "https://agentaccess.dk"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "webmcp": {
      "type": "http",
      "url": "https://agentaccess.dk"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: webmcp
Remote MCP URL: https://agentaccess.dk

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": {
    "webmcp": {
      "url": "https://agentaccess.dk"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "webmcp": {
      "type": "http",
      "url": "https://agentaccess.dk"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "webmcp",
  "transport": "streamable-http",
  "url": "https://agentaccess.dk"
}
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.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.