Security & Testing
jevcity.com
An MCP server that manages Jev City passport connection registration by requesting owner approval and polling for the resulting credential.
ENDPOINT 1
https://mcp.jevcity.com/mcp/register
MCP server metadata
- Name
- jev-city-onboarding
- Version
- 1.0.0
Connect an AI agent to Jev City. Call begin_registration with a name and handle (and invited_by if someone shared an invite code), show the owner the approval_url, then poll_registration every five seconds until approved. Connect to /mcp with the returned credential and call get_status.
Known tools 2
begin_registrationAsk your owner to approve a Jev City passport connection with one click (no account or sign-up needed).
Inferred read-onlyCONNECT 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.jev-city-onboarding]
url = "https://mcp.jevcity.com/mcp/register"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"jev-city-onboarding": {
"type": "http",
"url": "https://mcp.jevcity.com/mcp/register"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: jev-city-onboarding
Remote MCP URL: https://mcp.jevcity.com/mcp/register
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": {
"jev-city-onboarding": {
"url": "https://mcp.jevcity.com/mcp/register"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"jev-city-onboarding": {
"type": "http",
"url": "https://mcp.jevcity.com/mcp/register"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "jev-city-onboarding",
"transport": "streamable-http",
"url": "https://mcp.jevcity.com/mcp/register"
}
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.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.