CUSIP/ISIN Validator — Security Identifier Validation
@easysolutions906
About CUSIP/ISIN Validator — Security Identifier Validation
Validate and parse CUSIP and ISIN security identifiers using official checksum algorithms. Pure computation, no external dependencies. Used by trading platforms, portfolio tools, and fintech.
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"cusip": {
"command": "npx",
"args": [
"-y",
"@easysolutions906/mcp-cusip-isin"
]
}
}
}Tools
No tools detected
Fetch the live tool list by running this server in a temporary sandbox using the button above.
Overview
What is CUSIP/ISIN Validator — Security Identifier Validation?
A Model Context Protocol (MCP) server for validating and parsing CUSIP and ISIN security identifiers using check-digit algorithms. It provides four tools and a REST API for financial data applications that need to verify identifier integrity without external datasets.
How to use CUSIP/ISIN Validator — Security Identifier Validation?
Install via npx @easysolutions906/mcp-cusip-isin. For local use with Claude Desktop or Cursor, add the configuration shown in the README to your claude_desktop_config.json or .cursor/mcp.json. Set the PORT environment variable to run as an HTTP server, then use endpoints like `GET /cusip/validate?cusip
Basic information
More Developer Tools MCP servers

Skilder.ai
skilder.aiRun skills and MCP tools like production software: versioned, composed into roles, distributed to every agent from one governed library.

Air Pipe
airpipeBuild, validate, deploy — HTTP APIs, cron jobs, webhooks and MCP tools — from your AI client.
Agent Conductor
icohangar-opsAgent conductor — AGENTS.md contract parser, SKILL.md registry, CHP decision engine over MCP

Moxie Docs
Jackalope-DevAutomated codebase documentation for GitHub: searchable docs, MCP context for AI agents, doc drift detection, and Friday Cleanup PRs.

Routebase
RoutebaseRoutebase keeps your API's design, docs, contract tests, mocks and monitoring in one living OpenAPI spec so they can't drift apart. Agents work on that same source of truth, under your team's permissions.
Comments