Skip to content

modelcontextprotocol/specification

View on GitHub ↗Related repositories →

模型上下文协议规范(中文版)

active 2025-02-112025-04-08 (UTC)

Partial coverage11,782 / 13,132 hourly files (90%) · 2 absent upstream · 1,346 failed, retryable2025-02-092026-08-10 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
684
Pushes
4
Pull requests
13
Issues
18
Stars
444
Forks
55

Activity over time

Daily event counts in the loaded window

Line chart, 57 days from 2025-02-11 to 2025-04-08. Pushes: 4 total, peak 3 in a day. Pull requests: 13 total, peak 4 in a day. Issues: 18 total, peak 3 in a day. Comments: 113 total, peak 10 in a day. Stars: 444 total, peak 40 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

Recent activity

Latest issues, pull requests and releases

  • Issue comment#284nbarbettini2025-04-08 04:26
    [RFC] Update the Authorization specification for MCP servers
  • Issue comment#267hmd-ai2025-04-06 09:30
    Add HTTP-based implementation for Model Context Protocol
  • Issue comment#205DGuhr2025-04-05 20:23
    Treat the MCP server as an OAuth resource server rather than an authorization server
  • Issue comment#205aaronpk2025-04-05 20:10
    Treat the MCP server as an OAuth resource server rather than an authorization server
  • Issue comment#205DGuhr2025-04-05 20:04
    Treat the MCP server as an OAuth resource server rather than an authorization server
  • Issue comment#229michaelnugent2025-04-05 14:33
    Pagination for tool/call
  • Issue comment#271michaelnugent2025-04-05 14:28
    Create a single IETF RFC-style document that clearly describes the entire protocol
  • Pull request#280subomi2025-04-05 13:21
  • Issue#279pulkitsharma072025-04-05 12:57
    Formalise a way to request the tool parameter from a human
  • Issue comment#195rodocite2025-04-05 10:44
    Clients should support `WWW-Authenticate` for authentication rather than just the MCP server's OIDC metadata document
  • Issue#278qdrddr2025-04-05 01:23
    At the MCP Client side to selectivelly disable some of the tools from being listed
  • Issue comment#205ciamshrek2025-04-04 23:19
    Treat the MCP server as an OAuth resource server rather than an authorization server
  • Issue comment#277connor43122025-04-04 23:11
    Specify format for tool names
  • Issue comment#277kentcdodds2025-04-04 23:07
    Specify format for tool names
  • Issue#277kentcdodds2025-04-04 23:03
    Specify format for tool names
  • Issue comment#205dasiths2025-04-04 06:40
    Treat the MCP server as an OAuth resource server rather than an authorization server
  • Issue comment#205ayshsandu2025-04-04 06:08
    Treat the MCP server as an OAuth resource server rather than an authorization server
  • Issue comment#205simba-git2025-04-03 22:25
    Treat the MCP server as an OAuth resource server rather than an authorization server
  • Issue comment#221johnlanni2025-04-03 05:58
    add client crendentials grant type
  • Issue#271obinnaokechukwu2025-04-03 02:38
    Create a single IETF RFC-style document that clearly describes the entire protocol
  • Pull request#270max-stytch2025-04-03 01:58
  • Pull request#267ivikash2025-04-02 05:36
  • Issue comment#205lsimoneau2025-03-30 21:23
    Treat the MCP server as an OAuth resource server rather than an authorization server
  • Issue comment#206daviddenton2025-03-30 19:23
    [RFC] Replace HTTP+SSE with new "Streamable HTTP" transport
  • Issue comment#206hemanth2025-03-30 19:04
    [RFC] Replace HTTP+SSE with new "Streamable HTTP" transport

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 444 stars here means stars gained during the window, not the repo's star count.