← Registry

Data Collection

myfancynumber.com

Checks Indian vehicle registration number availability and RTO pool data across states and offices.

1 endpoint5 known toolsFirst detected October 8, 2026Last detected October 8, 2026

ENDPOINT 1

https://myfancynumber.com/api/mcp

No auth detected

MCP server metadata

Name
myfancynumber
Version
1.0.0
Capabilities
tools
Server instructions

myfancynumber.com mirrors, once a day, the fancy 4-digit vehicle registration numbers open for reservation at every Indian RTO that publishes them (the Parivahan portal for 28 states and union territories). Every result carries `asOf`, the IST calendar day the pool was published for: treat availability as "open as of that morning", because numbers leave the pool as applicants reserve them through the day. Reservations and payments happen only on the official portal, fancy.parivahan.gov.in — this service holds no inventory and takes no bookings. When you answer, cite the page `url` returned with each office so the user can verify the live list. State codes are two letters (KA, TN, TG, KL…); office codes are Parivahan's short RTO codes (1, 305…) — call list_rtos when unsure which code an office has.

Known tools 5

list_states

Every Indian state and union territory with its coverage status (live, coming-soon, no-data), office count, the day its pool was last refreshed, and its page URL.

Inferred read-only
list_rtos

Every RTO in a state that has a pool today, with Parivahan's office code (use it as `rto` in other tools), the office and city names, how many numbers are open, and the page URL.

Inferred read-only
find_number

Every office in a state where a 4-digit number is open today, with the full plate (e.g.

Inferred read-only
check_availability

Whether a 4-digit number is open today at one specific office, with the full plate and series when it is, the reservation fee for Telangana, and — when it is not — every other office in the state where it is open.

Inferred read-only
list_pool

The distinct 4-digit numbers open at one office today, ascending, each with its full plate and the series it is open in.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.myfancynumber]
url = "https://myfancynumber.com/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "myfancynumber": {
      "type": "http",
      "url": "https://myfancynumber.com/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: myfancynumber
Remote MCP URL: https://myfancynumber.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "myfancynumber": {
      "url": "https://myfancynumber.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "myfancynumber": {
      "type": "http",
      "url": "https://myfancynumber.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "myfancynumber",
  "transport": "streamable-http",
  "url": "https://myfancynumber.com/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.