Hosted MCP server/Search

Permit Scouter MCP server

Hosted at api.permitscouter.com·Streamable HTTP

Permit Scouter publishes building permits from ten Florida jurisdictions across Tampa Bay, Southwest and Central Florida, collected every morning and cleaned into one format. The API at https://api.permitscouter.com covers permit search, a single permit, address history and contractor records, with up to 25 results per call. Paid routes settle with x402 in USDC on Base: the first call returns HTTP 402 with a PAYMENT-REQUIRED header, the client signs a USDC authorization and retries with PAYMENT-SIGNATURE. There is no account or API key, and free sample routes let an agent try first. The service is in test mode on Base Sepolia until live launch.

api.permitscouter.com Streamable HTTP x402 pay-per-call (no account or key) Server not checked yet Reviewed 2026-11-16
About

Where it fits

Contractors, roofers and property researchers checking Florida permit history.

  • Search permits for a zip or city.
  • Read one permit record with its source URL.
  • Check a contractor's permit record.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds Permit Scouter as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http permit-scouter https://api.permitscouter.com/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://api.permitscouter.com/mcp
Host
api.permitscouter.com · /mcp
Transport
Streamable HTTP
Authentication
x402 pay-per-call (no account or key)
Server name
permit-scouter
Listing type
Community or directory listing

The installer uses the server name permit-scouter. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that permit-scouter appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Search permits for a zip or city. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Permit Scouter documentationhttps://permitscouter.com/docs