Permits Engine — Agent Market

io.github.USTechAutomationsPublished by GitHub account USTechAutomationsv0.1.0Updated Oct 24, 2026

Free MCP tools: permit quotes, jurisdiction index, track record, attestation.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint offering free tools for building-permit quotes, a jurisdiction index, a track record, and attestation.

What you can do
Get permit quotes through the server's free tools, as described in its registry listing. Look up jurisdictions in a permit jurisdiction index. Check a track record and an attestation, presumably about permit outcomes or the provider. The listing gives no tool names or parameter details, so the exact inputs and outputs are not documented here.
When to use it
Worth considering when an assistant needs quick, free permit-related lookups such as quotes or jurisdiction information, and a remote endpoint is acceptable. Not suitable where the workflow needs documented tool schemas or offline use.
Requirements
A remote streamable HTTP endpoint; the assistant connects to the provider's hosted address. No authentication, environment variables, or headers are declared, and no local package is needed.
Before you install
The listing is very thin: no tool schemas, README, or instructions are provided, so what each tool returns cannot be verified in advance. Quotes and track-record data come from a third party and should be confirmed before relying on them for real permit decisions.

Installation

In SourceWeft

  1. Open Permits Engine — Agent Market in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.USTechAutomations%2Fusta-agent-market-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "permits-engine-agent-market": {
      "type": "http",
      "url": "https://agents.ustechautomations.com/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.