Bilibii Mcp Server

Created By
treea year ago
这是一个基于Model Context Protocol (MCP)的服务,用于查询B站用户的粉丝数量。通过提供B站用户ID,可以获取该用户的粉丝数。
Overview

what is Bilibili MCP Server?

Bilibili MCP Server is a service based on the Model Context Protocol (MCP) that allows users to query the follower count of Bilibili users by providing their user ID.

how to use Bilibili MCP Server?

To use the Bilibili MCP Server, clone the repository, install the dependencies, and start the server. Then, use the MCP Inspector to test the getBilibiliFollowerCount tool by entering the user ID of the Bilibili user.

key features of Bilibili MCP Server?

  • Directly query Bilibili user follower counts using user IDs.
  • Supports MCP protocol for integration with large models like Claude and GPT.
  • Includes error handling and detailed logging.

use cases of Bilibili MCP Server?

  1. Checking the follower count of popular Bilibili content creators.
  2. Analyzing follower trends for Bilibili users.
  3. Integrating with other applications to provide follower count data.

FAQ from Bilibili MCP Server?

  • Why do I need to use user IDs instead of usernames?

Bilibili API directly supports querying by user ID, which is more reliable and efficient. Usernames may change or be duplicated, while IDs are unique.

  • How does the service handle API request failures?

The service automatically retries and logs detailed error information, which can be found in the logs directory.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tree
Star
-
Language
-
License
-

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

13 hours ago