Nummeropslag MCP server
io.github.andrey-tut/nummeropslag·v1.0.2Privacy-first Danish caller ID, CVR company lookup, operator data, and community spam signals.
0 stars
Reviews
Write oneNobody has reviewed Nummeropslag yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Nummeropslag tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 50 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Nummeropslag compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 65/100
- higher than 20% of 48,255 servers
Install Nummeropslag in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Nummeropslag repository's README, as published. We do not edit it. Read it on GitHub
Nummeropslag API
Public Partner API + MCP server for Danish phone-number lookup, caller-ID and spam/trust signals.
<!-- mcp-name: io.github.andrey-tut/nummeropslag -->
Identify who is calling from a Danish number: company from the official CVR register, telecom operator, number type, and a spam/trust verdict based on anonymous user reports. Powered by official open data — not scraping. Use it from any HTTP client, or plug the MCP server straight into Claude and other AI agents.
🌐 Service: nummeropslag.dk · 🔑 Get a key: /api-noegle · 📖 API reference: Redoc · 🧪 Live sandbox: /api-reference · 🤖 MCP
This repository contains only public API docs, the OpenAPI spec, client examples and the MCP server. The backend source is private.
Authentication
All endpoints require an API key, sent in the X-API-Key header:
X-API-Key: npk_your_key_hereEach key has a plan, a set of scopes (lookup, spam, operator) and a request quota. Check your key status any time via GET /api/v1/partner/me.
Base URL: https://nummeropslag.dk/api/v1
Endpoints
{e164} accepts an 8-digit Danish number or full E.164 — e.g. 33633363 or +4533633363.
Full machine-readable contract: openapi/openapi.yaml · openapi/openapi.json.
Quick start
export NUMMEROPSLAG_API_KEY=npk_your_key_here
curl -H "X-API-Key: $NUMMEROPSLAG_API_KEY" \
https://nummeropslag.dk/api/v1/partner/spam/33633363Client examples
Ready-to-run, dependency-free clients in examples/:
All read the key from the NUMMEROPSLAGAPIKEY environment variable.
Workflow integrations
Use Nummeropslag as native nodes and tools in popular automation and AI workflow builders:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Nummeropslag: common questions
- Is Nummeropslag MCP server safe?
- With care: it is graded C, so read the findings first (65/100). Read the Nummeropslag safety report
- Does Nummeropslag need an API key?
- Yes. The registry entry asks for
NUMMEROPSLAG_API_KEY. - Is Nummeropslag maintained?
- The last commit was 92 days ago (2026-08-04). The latest release is v1.0.2.