3GPPSAFE
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Transform your AI assistant into a 3GPP specification expert with direct access to TSpec-LLM's 535M word dataset!
[](https://modelcontextprotocol.io/) [](https://nodejs.org/) [](https://opensource.org/licenses/BSD-3-Clause)
What This Does
Before: Ask AI about 3GPP specifications - Get generic responses based on training data After: Ask AI + 3GPP MCP Server V3.0.0 - Get direct access to current specification content with structured, agent-ready responses
Revolutionary V3.0.0 Architecture
V3.0.0 represents the True MCP approach - lightweight API bridge providing direct specification data:
Agent Query → MCP Tools → External APIs → Real Specification Data
Key Benefits:
- True MCP Architecture - Lightweight API bridge (~10MB vs 15GB+)
- Sub-500ms responses - Intelligent caching with external API integration
- Agent-optimized - Structured JSON responses for AI agent consumption
- Real specification data - Direct access to TSpec-LLM's 535M word dataset
- External API integration - Hugging Face + 3GPP.org APIs
- Infinite scalability - Stateless API calls, no local storage limits
Quick Start (30 Seconds!)
Direct MCP Setup (Recommended)
Claude Desktop users:
claude mcp add 3gpp-server npx 3gpp-mcp-charging@latest serve
For other MCP clients: Add this to your MCP configuration:
{
"mcpServers": {
"3gpp-server": {
"command": "npx",
"args": ["3gpp-mcp-charging@latest", "serve"],
"description": "3GPP MCP Server - Direct access to TSpec-LLM and 3GPP specifications",
"env": {
"HUGGINGFACE_TOKEN": "optional-for-enhanced-access"
}
}
}
}Al
f960d59f5d2fOBSERVED · 2026-10-09Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add 3gpp-mcp-charging --env HUGGINGFACE_TOKEN=${HUGGINGFACE_TOKEN} -- npx -y [email protected]{
"mcpServers": {
"3gpp-mcp-charging": {
"command": "npx",
"args": [
"-y",
"[email protected]"
],
"env": {
"HUGGINGFACE_TOKEN": "${HUGGINGFACE_TOKEN}"
}
}
}
}Exposed tools (18)
18 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
Accounting | read | Diameter accounting for offline charging |
Authentication | read | Mutual authentication between UE and network |
Registration | read | UE registration with the network |
compare_specifications | read | Template for comparing two specifications with structured analysis of differences and relationships |
comparison_aspects | read | Specific aspects to compare (e.g., functionality, architecture, evolution) |
detail_level | read | Level of detail: overview, detailed, or implementation |
explain_3gpp_procedure | read | Template for explaining specific 3GPP procedures in detail with context and examples |
explain_3gpp_structure | read | Provides educational content about 3GPP organization, specification series, and working groups |
find_implementation_requirements | read | Extract detailed implementation requirements for specific 3GPP features, including mandatory/optional requirements, dependencies, and implementation guidance. |
generate_research_strategy | read | Creates comprehensive research approaches for complex 3GPP topics with phased methodology |
get_specification_details | read | Get comprehensive details about a specific 3GPP specification including metadata, content, dependencies, and related information. |
guide_specification_search | read | Helps users formulate effective specification searches and provides targeted guidance for finding relevant 3GPP specifications |
map_requirements_to_specs | read | Maps technical requirements to appropriate 3GPP specifications with reading order and implementation guidance |
procedure_name | read | Name of the 3GPP procedure to explain |
search_specifications | read | Search 3GPP specifications using TSpec-LLM dataset and official metadata. Returns actual specification content and structured metadata for agent consumption. |
spec_a | read | First specification to compare |
spec_b | read | Second specification to compare |
specification | read | Relevant specification (e.g., TS 24.501) |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (2 observation(s))
- Shell
- declared (2 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (1)
@modelcontextprotocol/sdk, commander, inquirer, chalk, ora, boxen, axios, node-cache
Gates applied: no_behavioural_pass.
f960d59f5d2ffull audit observations/trust-audit/mcp-server/edhijlu__3gpp.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | f960d59f5d2f | SAFE | B | 89 | first audit |
Questions
What tools does 3GPP expose?
18 in total: 18 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is 3GPP safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does 3GPP need?
It reads HUGGINGFACE_TOKEN from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does 3GPP run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as 3gpp-mcp-charging at 3.0.2.
How current is this page?
The grade is for one exact copy of the source (f960d59f5d2f), read on 2026-10-09. The repository is watched and re-audited when it changes.