Item detail
github.com

sv-number/mcp-server

sv-number/mcp-server is an MCP server in RepoRadar's Radar section, holding Bronze tier and a 'watch' verdict. Its strongest signal is open-source/build quality, scored 8.4 out of 10.

Score6.2
Popularity0.0
Riskmedium
TierBronze
Score breakdown
Usefulness6.2
Novelty4.5
Momentum3.5
Maturity4.6
Open-source/build8.4
Evidence7.2
Workflow potential7.0
Setup ease8.0

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Most agent flows handle verification codes by reading email or asking the user to copy a number. sv-number gives the agent itself a disposable private number and the parsed code, which is a clean primitive for sign-up, account-takeover testing, and headless sign-in flows where the user has approved the action up front.

Where this stands now

sv-number/mcp-server ranks #1116 of 2770 tracked Radar items by composite score (6.2 against a section median of 4.9). The section currently carries 1659 Bronze, 645 Gold, 466 Silver. RepoRadar has retained observations for this record since 2026-08-10 (54 days in the current window). Signal extremes versus the section: momentum at the 30th percentile.

Who should use it

Software developers Engineering teams

Who should skip it

Hold off on sv-number/mcp-server for mission-critical workflows without a containment strategy, explicit approvals, and a hands-on security review.

About this signal

sv-number/mcp-server is tracked by RepoRadar as an MCP server in the Radar section. First seen 2026-08-10; the source record was last checked on 2026-08-21. The current verdict is 'watch' with a Bronze tier and easy setup difficulty. The standout signals for sv-number/mcp-server are open-source/build quality (8.4) and setup ease (8.0), while momentum (3.5) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar captured from https://github.com/sv-number/mcp-server.

How this item is evaluated

The sv-number/mcp-server record combines a 6.2/10 composite score with separate popularity (0.0), risk (medium), and setup (easy) signals. See the scoring methodology for the current weights and evidence definitions.

Questions worth asking before you adopt this

Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.

Risk explanation

oauth_or_account_access; sends_email_or_messages; requires_api_key; scraping_or_surveillance.

Evidence links
Closest alternatives / related signals
mcp phone-number sms-verification typescript stdio otp scout-staged
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-10-03T17:13:14.190776Z.

No editorial or hands-on review is claimed. This record remains at Discovered.

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

31 dated snapshots retained from 2026-08-26 through 2026-10-03; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score6.2 current · +0.0 net
Repository momentum5.5 current · -2.0 net
GitHub stars (observed)547 current · -12 net
GitHub stars547 exact observation
VersionNot reported by source
Last releaseNot reported by source
Maintenancemaintained
Current riskMedium
Current verdictWatch
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineClaude, Claude Code, Model Context Protocol

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-10-036.25.5547MediumWatchmaintained
2026-10-026.25.5547MediumWatchmaintained
2026-10-016.25.5547MediumWatchmaintained
2026-09-306.25.5551MediumWatchmaintained
2026-09-296.25.5551MediumWatchmaintained
2026-09-286.25.5551MediumWatchmaintained
2026-09-276.25.5551MediumWatchmaintained
2026-09-266.25.5551MediumWatchmaintained
2026-09-256.25.5551MediumWatchmaintained
2026-09-246.25.0551MediumWatchmaintained
2026-09-236.25.5552MediumWatchmaintained
2026-09-226.25.5551MediumWatchmaintained

Why the record changed

Stars change

Stars changed: 551 → 547.

Stars change

Stars changed: 552 → 551.

Stars change

Stars changed: 551 → 552.

Stars change

Stars changed: 550 → 551.

Stars change

Stars changed: 551 → 550.

Stars change

Stars changed: 555 → 551.

Maintenance change

Maintenance changed: Active → maintained.

Stars change

Stars changed: 562 → 555.

Stars change

Stars changed: 558 → 561.

Stars change

Stars changed: 559 → 558.