← Registry

General Tools

projectpermit-api-v2-production.up.railway.app

Provides general-purpose tools through the Model Context Protocol.

1 endpoint3 known toolsFirst detected August 30, 2026Last detected August 30, 2026

ENDPOINT 1

https://projectpermit-mcp-production.up.railway.app/mcp

No auth detected

MCP server metadata

Name
ProjectPermit
Capabilities
experimentalpromptsresourcestools
Server instructions

Municipal construction permit preflight for supported Canadian cities. Use it when proposed renovation/building work needs an evidence-linked permit-applicability check before quoting, scheduling or design lock. Start with projectpermit_info to discover supported jurisdiction ids, project families and valid examples. Normalize the proposed scope into structured facts before calling check_project_requirements, or use check_project_requirements_batch for up to 50 normalized projects. Results include deterministic workflow guidance plus a platform-neutral action_bundle containing decision/routing, proposed tasks, official evidence, audit metadata, deterministic decision identity, duplicate-suppression idempotency and a safe writeback mutation gate. For repeated checks of the same work record, pass the prior action_bundle.identity as context.prior_decision_identity to receive change.classification and NOOP_UNCHANGED when appropriate. A READY mutation gate does not execute a write; an authorized integration must still explicitly request an atomic upsert by idempotency_key. Preserve unknown facts rather than guessing them; the engine can return review or municipal-confirmation states when the facts do not support a safe yes/no. Do not use ProjectPermit as municipal authorization, legal advice, engineering review, plan/code review, permit filing or inspection approval.

Known tools 3

projectpermit_info

Use first to get supported Canadian cities/families, identity/idempotency and safe-writeback semantics.

Inferred read-only
check_project_requirements

Use for proposed work before quoting/scheduling.

Inferred read-only
check_project_requirements_batch

Evaluate 1-50 normalized projects in one call.

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.projectpermit]
url = "https://projectpermit-mcp-production.up.railway.app/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "projectpermit": {
      "type": "http",
      "url": "https://projectpermit-mcp-production.up.railway.app/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: projectpermit
Remote MCP URL: https://projectpermit-mcp-production.up.railway.app/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": {
    "projectpermit": {
      "url": "https://projectpermit-mcp-production.up.railway.app/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "projectpermit": {
      "type": "http",
      "url": "https://projectpermit-mcp-production.up.railway.app/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "projectpermit",
  "transport": "streamable-http",
  "url": "https://projectpermit-mcp-production.up.railway.app/mcp"
}
MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for railway.app was fetched 2026-08-25T20:04:34.605Z.

Trust status Trusted

railway.app is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

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