pulsemcp Safe content atomic mcp-remote

atPlatform

This MCP server provides AI assistants with access to the atPlatform ecosystem for decentralized data sharing and storage, built using Dart with the at_client SDK and dart_mcp library for protocol integration. The implementation offers two core tools for listing atKeys with filtering by shared relationships and regex patterns, and retrieving atKey values with binary data detection, plus serves comprehensive atPlatform documentation as markdown resources covering protocol specifications, SDK usage, and authentication workflows. Built with custom logging integration, configurable root domain/port settings, and local atSign key management through the at_onboarding_cli, it serves developers building atPlatform applications who need conversational access to atSign data operations, teams exploring decentralized identity solutions, and AI assistants requiring detailed atPlatform documentation to guide users through implementation and troubleshooting of atSign-based applications.

Cognium trust score

30%

Tier

Unverified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-01.

Scan details: Circle-IR · 2026-09-01 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: monitoring
Source: PulseMCP
Repository: github.com/zambrella/at_mcp_server
Author type: human
Last scanned: 2026-09-01
Updated: 2026-09-01

View source Find related skills

MCP

Resolve atPlatform from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"