vanity-phone-number (MarioGiancini/vanity-phone-number) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 5 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

vanity-phone-number

Spell, test, and generate memorable vanity phone numbers. Local-first and agent-native (REST + MCP). Open source, MIT.

→ MarioGiancini/vanity-phone-number· listed on github_repo_search

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

MarioGiancini

Source: github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: VANITY_AGENT_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 6 credentials: AGENT_API_KEY, TELNYX_API_KEY, TWILIO_API_KEY, TWILIO_API_SECRET, TWILIO_AUTH_TOKEN, VANITY_AGENT_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

lowvitest@4.1.10GHSA-82fw-gwwq-j7x9

Vitest: Path Traversal / Arbitrary File Read via @vitest/mocker Redirect Mock

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretAGENT_API_KEY
configPLAYWRIGHT_PORT
🔐 secretTELNYX_API_KEYAvailability + discovery via Telnyx (second provider)
configTELNYX_MOCKDeterministic fake availability for local demos/tests
configTWILIO_ACCOUNT_SIDAvailability + discovery via Twilio (preferred: scoped, rotatable API key)
🔐 secretTWILIO_API_KEYAvailability + discovery via Twilio (preferred: scoped, rotatable API key)
🔐 secretTWILIO_API_SECRETAvailability + discovery via Twilio (preferred: scoped, rotatable API key)
🔐 secretTWILIO_AUTH_TOKENAvailability via Twilio (alternative: full-account auth token)
configTWILIO_MOCKDeterministic fake availability for local demos/tests
🔐 secretVANITY_AGENT_API_KEYAuth: Authorization: Bearer $ or x-api-key. If the key isn't set on the
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployNEXT_PUBLIC_SITE_URL
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

5/5 tools missing one or more hints — find_vanity_numbers (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); find_available_numbers (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); decode_number (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +2 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 2 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/mariogiancini/vanity-phone-number)](https://m8ven.ai/mcp/mariogiancini/vanity-phone-number)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 02e18070150bb2ea981211ad71a05d38b838c8dc
code hash: f15c5bca9151c805944ade6942ed4cfec8e2712aa70c27e162a8114d024302ac
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client