pulsemcp verified Safe content atomic mcp-remote

3GPP Research Guidance

This 3GPP MCP server by edhijlu provides intelligent guidance for telecommunications standards research through a lightweight knowledge-driven architecture that stores structured metadata about 3GPP specifications rather than hosting content. Built with TypeScript and featuring a guidance engine, knowledge base, and template generator, it offers tools for specification discovery, 3GPP structure explanation, requirements-to-specs mapping, and research strategy generation, with adaptive responses based on user expertise level (beginner/intermediate/expert). The implementation focuses on educational methodology over data retrieval, using compact knowledge representation to achieve sub-500ms response times while consuming under 100MB memory, making it ideal for telecom engineers, researchers, and students who need strategic guidance for navigating 3GPP's complex specification ecosystem without requiring massive local storage or external API dependencies.

Cognium trust score

89%

Tier

Verified

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-28.

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

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: media
Source: PulseMCP
Repository: github.com/edhijlu/3gpp-mcp-server
Author type: human
Last scanned: 2026-09-28
Updated: 2026-09-28

View source Find related skills

MCP

Resolve 3GPP Research Guidance 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"