_ registry / mcp + a2a streamable-http · checked 1h ago

p0stman MCP Server

https://p0stman.com

Registry code: 52ca7f78e9fc514f

api record

Server for p0stman, a product development studio: browse services, portfolio and guides, book a discovery call or submit a project inquiry.

endpoint
https://p0stman.com/api/mcp
door code
35a66fd87cae72c1
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is p0stman MCP Server live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is p0stman MCP Server free to use?
Yes — the hub reached it with no key and no payment.
What tools does p0stman MCP Server have?
5 tools: submit_inquiry, search_content, book_discovery_call, get_services, get_portfolio.
Is p0stman MCP Server safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.6%· all time 99.8%

latency
298ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 670 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
productivity & business
used for
  • browse agency services and pricing
  • view portfolio case studies
  • book a discovery call
  • submit a project inquiry
takes → gives
text → data
tools
3 reads1 changes data1 sends messages
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
2 open 3 never probed 2 of 5 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_services reads open 18h ago

    Get list of p0stman services with pricing and timelines.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "category": {
      "type": "string",
      "description": "Filter by category (optional)"
    }
  }
}
    arguments 9 lines
  • get_portfolio reads open 18h ago

    Get p0stman case studies and portfolio of shipped products.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "industry": {
      "type": "string",
      "description": "Filter by industry (optional)"
    }
  }
}
    arguments 9 lines
  • submit_inquiry sends messages unknown never probed

    Submit a project inquiry to p0stman. Use this for detailed enquiries or when the user wants to get in touch.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name",
    "email",
    "message"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Your full name"
    },
    "email": {
      "type": "string",
      "description": "Your email address"
    },
    "message": {
      "type": "string",
      "description": "Your message or project description"
    },
    "project_type": {
      "type": "string",
      "description": "Type of project (e.g. AI voice agent, MVP, web app)"
    }
  }
}
    arguments 26 lines
  • search_content reads unknown 18h ago

    Search p0stman guides, comparisons, and content pages.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Search query"
    }
  }
}
    arguments 12 lines
  • book_discovery_call changes data unknown never probed

    Book a free 30-minute discovery call with Paul at p0stman to discuss your project.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name",
    "email",
    "project_description"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Your full name"
    },
    "email": {
      "type": "string",
      "description": "Your email address"
    },
    "preferred_time": {
      "type": "string",
      "description": "Preferred time or timezone (optional)"
    },
    "project_description": {
      "type": "string",
      "description": "Brief description of your project or idea"
    }
  }
}
    arguments 26 lines
_ try it over mcp 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.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 52ca7f78e9fc514f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/52ca7f78e9fc514f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/52ca7f78e9fc514f/badge.svg)](https://brick.blue/agent/52ca7f78e9fc514f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
90%

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.