_ registry / mcp streamable-http · checked 16h ago

outsend

https://outsend.xyz

Registry code: c849e75740d03d87

api record

outsend extracts B2B prospecting data (Google Maps + enrichment). Start with list_modules. Jobs are ASYNC: create, then poll get_job until done, then get_job_results (preview + download link — never paste thousands of rows). Estimate big scrapes first with estimate_scrap; use stop_at when the user wants ~N results.

endpoint
https://outsend.xyz/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
159ms

last good check

priced tools
0

of 13 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 13 tools
13 auth-required 13 of 13 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_pipeline_schema auth-required 16h ago

    Machine contract for building pipelines: valid block types, per-block config schema, and chaining rules. Use before create_pipeline.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • list_modules auth-required never probed

    Catalog of outsend data modules: what each one needs and produces. Call this first to know what is possible. Modules listed as coming_soon cannot be launched.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • estimate_scrap auth-required never probed

    Estimate the cost (EF) and volume of a Google Maps extraction WITHOUT launching it. Always estimate before creating a large job. 1 EF = a full-France scrape for one query type.

    mcp-tool

    {
  "type": "object",
  "required": [
    "queries",
    "zones"
  ],
  "properties": {
    "zones": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 50,
      "minItems": 1,
      "description": "Cities, departments, regions or 'France'"
    },
    "country": {
      "type": "string",
      "description": "ISO3 country code, default FRA"
    },
    "queries": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 20,
      "minItems": 1,
      "description": "Business types, e.g. ['plombier', 'electricien']"
    },
    "stop_at": {
      "type": "integer",
      "minimum": 1,
      "description": "Stop after N unique places (recommended when the user gives a number)"
    },
    "scrap_mode": {
      "enum": [
        "fast",
        "normal",
        "ultra"
      ],
      "type": "string"
    }
  }
}
    arguments 44 lines
  • create_scrap_job auth-required never probed

    Launch a Google Maps extraction (async). Returns the job id immediately; poll get_job until status=done, then use get_job_results. When the user wants ~N results, set stop_at.

    mcp-tool

    {
  "type": "object",
  "required": [
    "queries",
    "zones"
  ],
  "properties": {
    "zones": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 50,
      "minItems": 1
    },
    "country": {
      "type": "string",
      "description": "ISO3, default FRA"
    },
    "queries": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 20,
      "minItems": 1
    },
    "stop_at": {
      "type": "integer",
      "minimum": 1
    },
    "scrap_mode": {
      "enum": [
        "fast",
        "normal",
        "ultra"
      ],
      "type": "string"
    },
    "extra_columns": {
      "type": "array",
      "items": {
        "enum": [
          "gps",
          "departement",
          "region"
        ],
        "type": "string"
      }
    },
    "max_per_phone": {
      "type": "integer",
      "minimum": 0
    }
  }
}
    arguments 56 lines
  • create_enrichment_job auth-required never probed

    Enrich the results of a finished job (async): find emails, scrape reviews, detect social networks, verify emails, tech stack, etc. Returns the new job id.

    mcp-tool

    {
  "type": "object",
  "required": [
    "enrichment",
    "source_job_id"
  ],
  "properties": {
    "email_mode": {
      "enum": [
        "normal",
        "deep"
      ],
      "type": "string",
      "description": "Only for enrichment=emails. Default normal."
    },
    "enrichment": {
      "enum": [
        "ads_intelligence",
        "brand_assets",
        "dead_check",
        "emails",
        "legal_data",
        "legal_ids",
        "legal_mentions",
        "pagespeed",
        "phone_info",
        "phones_extra",
        "pricing",
        "reviews",
        "socials",
        "techstack",
        "verify_emails"
      ],
      "type": "string"
    },
    "source_job_id": {
      "type": "string",
      "description": "A job with status=done"
    }
  }
}
    arguments 41 lines
  • get_job_results auth-required never probed

    Preview of a finished job's rows (max 50 per call, paginate with offset) + total count + CSV download URL. Never dump thousands of rows into the conversation: show a sample, give the link.

    mcp-tool

    {
  "type": "object",
  "required": [
    "job_id"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1
    },
    "job_id": {
      "type": "string"
    },
    "offset": {
      "type": "integer",
      "minimum": 0
    }
  }
}
    arguments 20 lines
  • list_jobs auth-required 16h ago

    The account's recent jobs, newest first.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1
    }
  }
}
    arguments 10 lines
  • create_pipeline auth-required never probed

    Create AND start a multi-step pipeline (e.g. scrap → emails → verify_emails). Keep chains LINEAR (each block feeds the next). Edges use the keys "from" and "to" — NOT source/target. Call get_pipeline_schema first for the valid block types and their config fields. Returns pipeline id + initial job ids. Example definition: {"nodes": [{"id": "n1", "type": "scrap", "config": {"queries": ["plombier"], "zones": ["Lyon"], "stop_at": 500}}, {"id": "n2", "type": "emails", "config": {}}], "edges": [{"id": "e1", "from": "n1", "to": "n2"}]}

    mcp-tool

    {
  "type": "object",
  "required": [
    "definition"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 100
    },
    "definition": {
      "type": "object",
      "required": [
        "nodes"
      ],
      "properties": {
        "edges": {
          "type": "array",
          "items": {
            "type": "object"
          }
        },
        "nodes": {
          "type": "array",
          "items": {
            "type": "object"
          }
        }
      },
      "description": "{nodes: [{id, type, config}], edges: [{id, from, to}]} — edge keys are \"from\"/\"to\", not source/target"
    }
  }
}
    arguments 33 lines
  • list_pipelines auth-required never probed

    The account's pipelines with status.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • create_veille auth-required never probed

    Turn a finished job or pipeline into recurring monitoring: outsend re-runs it every N days and computes the diff (new / removed / modified places).

    mcp-tool

    {
  "type": "object",
  "required": [
    "name",
    "frequency_days"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1
    },
    "source_job_id": {
      "type": "string"
    },
    "frequency_days": {
      "type": "integer",
      "maximum": 90,
      "minimum": 1
    },
    "source_pipeline_id": {
      "type": "string"
    }
  }
}
    arguments 25 lines
  • list_veilles auth-required never probed

    The account's recurring monitors.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_job auth-required never probed

    Status, counters and download URL of a job.

    mcp-tool

    {
  "type": "object",
  "required": [
    "job_id"
  ],
  "properties": {
    "job_id": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • get_events auth-required 16h ago

    Account event feed (job.completed, pipeline.completed, veille.run_completed…). Cursor-based: pass back last_id as since_id.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1
    },
    "types": {
      "type": "array",
      "items": {
        "type": "string"
      }
    },
    "since_id": {
      "type": "integer",
      "minimum": 0
    }
  }
}
    arguments 20 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c849e75740d03d87/badge.svg)](https://brick.blue/agent/c849e75740d03d87)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.