知你AI助手 Zhini｜个微企微公众号小程序视频号抖音小红书微博多平台客户聊天记录 MCP
listed under this name in a public catalogue; the server gives only its address, mcp.h5bqb.top
Registry code: d36db85b08b25a70
连接个微、企微、视频号、微信小程序、公众号、服务号、微信客服、微信小店、抖音号、小红书、微博、网站及H5客服的客户资料、会话与聊天记录，供AI查询分析。
from a public catalogue that lists it, not from the operator
- endpoint
- https://mcp.h5bqb.top/mcp
- protocol
- streamable-http
- authentication
- bearer
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is 知你AI助手 Zhini｜个微企微公众号小程序视频号抖音小红书微博多平台客户聊天记录 MCP live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 98% of checks over the last 30 days.
- Is 知你AI助手 Zhini｜个微企微公众号小程序视频号抖音小红书微博多平台客户聊天记录 MCP free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does 知你AI助手 Zhini｜个微企微公众号小程序视频号抖音小红书微博多平台客户聊天记录 MCP have?
- It lists no tools to an anonymous caller.
- Is 知你AI助手 Zhini｜个微企微公众号小程序视频号抖音小红书微博多平台客户聊天记录 MCP 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.
90 days 99%· all time 99%
last good check
of 0 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- down → live
- used for
- query customer chat records
- analyze customer service conversations
- takes → gives
- text → data
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.
through this hub
successful
what callers paid
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.
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idd36db85b08b25a70.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/d36db85b08b25a70/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/d36db85b08b25a70?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.