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

知你AI助手|多平台客户与客服数据 MCP

listed under this name in a public catalogue; the server gives only its address, ai.zhinikefu.com

https://ai.zhinikefu.com

Registry code: bcbffa4a4dee22f6

api record

知你AI助手 MCP 将知你客服中的多平台账号、客户资料、当前与历史会话及聊天记录连接到 Codex、Claude Code、WorkBuddy 等 AI 工具,让客服、销售、运营和产品团队通过自然语言完成客户查询、会话研判、历史记录检索、客户分群与业务分析。 支持个微、企微、视频号、微信小程序、公众号、服务号、微信客服、微信小店、抖音号、小红书、微博、网站及 H5 客服等平台渠道。 核心能力: - 统一查询多平台客户资料、标签、来源渠道、负责人和联系信息 - 查看待接待、我的会话、同事会话及 AI 会话 - 按姓名、手机号、微信号、渠道、客服、标签和时间搜索客户 - 按退款、投诉、报价、试用、购买等关键词检索历史会话 - 读取完整消息上下文,辅助客服分诊、销售跟进、运营洞察和问题复盘 - 查询 API Key 总额度、已使用量和剩余额度 使用方法:访问…

from a public catalogue that lists it, not from the operator

endpoint
https://ai.zhinikefu.com/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 it live, free and safe measured by this hub
Is 知你AI助手|多平台客户与客服数据 MCP live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is 知你AI助手|多平台客户与客服数据 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助手|多平台客户与客服数据 MCP have?
It lists no tools to an anonymous caller.
Is 知你AI助手|多平台客户与客服数据 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.
reachable
live
uptime, 30 days
99.2%

90 days 99.6%· all time 99.6%

latency
834ms

last good check

priced tools
0

of 0 tools

_ answered our checks, 90 days 230 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • search customer profiles across chat platforms
  • review customer conversations
  • segment customers
takes → gives
text → data, text
_ 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 0 tools
0 of 0 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.

_ 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.

_ 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 bcbffa4a4dee22f6.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/bcbffa4a4dee22f6/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/bcbffa4a4dee22f6/badge.svg)](https://brick.blue/agent/bcbffa4a4dee22f6?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 know
card completeness
20%

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.