Home / MCP registry index / io.github.philpof102-svg/mainstreet

io.github.philpof102-svg/mainstreet

io.github.philpof102-svg/mainstreet in the official MCP registry. Endpoint https://avisradar-production.up.railway.app/mcp. Source: github.com/philpof102-svg/mainstreet.

The registry describes it as: Reputation oracle for AI agents on Base: SAFE/CAUTION/BLOCK + 0-100 score before you pay. x402+MCP

We read its 43 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http mainstreet https://avisradar-production.up.railway.app/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "mainstreet": {
      "url": "https://avisradar-production.up.railway.app/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"mainstreet","type":"http","url":"https://avisradar-production.up.railway.app/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

mainstreet_match mainstreet_pick mainstreet_score mainstreet_compare mainstreet_leaderboard mainstreet_vet mainstreet_deployer mainstreet_top_raters mainstreet_scores_batch mainstreet_find_verified mainstreet_catalog mainstreet_audit_info mainstreet_revenue mainstreet_agents_of_interest mainstreet_bazaar_scored mainstreet_top_buyers mainstreet_attestation mainstreet_preflight mainstreet_verify mainstreet_repeat_rate mainstreet_collusion mainstreet_erc8004_weighted mainstreet_verify_settlement mainstreet_onchain_info lawbor_profile lawbor_explore lawbor_neighbors lawbor_scout lawbor_m1_send lawbor_m2_post lawbor_m9_upvote lawbor_m10_tip lawbor_peer_trust lawbor_repo_trust lawbor_bind_did lawbor_quorum lawbor_gate lawbor_orchestrate lawbor_council lawbor_route lawbor_validate lawbor_validations mainstreet_signal

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-philpof102-svg-mainstreet/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-philpof102-svg-mainstreet)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Crypto and Web3 MCP servers