Every change Wellknown observed on this MCP server, newest first, with what it was before and what it became. Tool-surface changes carry the definition diff. Nothing here is edited after the fact.
Added "find_rfp_for_idea", "get_dev_fund_activity", "get_dev_fund_person" and 6 more; changed the definition of "community_consensus" and "semantic_search" (90 tools before, 99 now)
Surface signals of what the Canton community thinks about a topic: the forumthreadthreadsreplythatratiosmatch it best (views, replies, distinct participants), mailing list debate volume, and the first reply on themost-viewedbest-matching thread. Canton-specific. Not sentiment-analysis; a structured roundup the caller can summarise.
⟨76 unchanged words⟩ is a released package version from the npm/Dockerregistries.registries; \"dev_fund_comment\" is a comment, review or inline review comment on a Dev Fund PR; \"dev_fund_file\" is a proposal file. Omit for all.","items":{"enum": ⟨13 unchanged words⟩ ","gov_vote","radar_item","cip_attachment","sdk_version","dev_fund_comment","dev_fund_file"],"type":"string"},"type": ⟨5 unchanged words⟩
Given a project idea, find which Canton Dev Fund RFP(s) it fits and how crowded that area is. Matches the idea against the RFP texts in the 2026-2028 roadmap (shared terms, shown), then for the best fits shows what the Foundation asks for, its stated appetite for grants, and the proposals that declare the RFP. Also shows the existing Dev Fund proposals closest to the idea by text whether or not they declared an RFP, because most never did. The match is lexical, so a fit with few shared terms is weak and flagged as such. If no RFP fits, the idea can still be filed as an individual initiative (…
What happened in the Canton Dev Fund lately, newest first: new comments and reviews with a snippet, and (optionally) timeline events such as labels added, reviewers requested, proposals renamed, merged, closed or moved on the project board. Use for "what is going on in the Dev Fund", "what did the committee say this week", "which proposals just got reviewed". Canton-specific.
Who is this person in the Canton Dev Fund, by GitHub login: their SIG memberships and organization (from the SIG directory), the proposals they authored, how much they comment and review (and how often they approve or request changes), which proposals asked them to review, which they were assigned, and where a champion line names them. Use to judge who a possible champion or reviewer is and how responsive they are. Canton-specific.
Everything CCPEDIA holds about ONE Canton Dev Fund proposal (a pull request in canton-foundation/canton-dev-fund), by its PR number: state and project-board column, labels, the facts parsed from the proposal file (organization, author, declared RFP, champion, funding in CC, duration, SIG label, milestones), champion evidence (board column, proposal file, PR text), reviewers, discussion statistics, and the timeline of label, reviewer, rename and board events. Use after get_proposals, list_proposals_needing_champion or search_dev_fund returned a number. For the full conversation use get_proposa…
The conversation on ONE Canton Dev Fund proposal, oldest first: every comment, every formal review (approved, changes requested, commented) and every inline review comment on the proposal file, with author, GitHub role (member, collaborator, none), date, and the text. Pages with offset. Use to read what reviewers, champions and the committee actually said, or why a proposal stalled. Canton-specific.
The full text of the proposal file(s) a Canton Dev Fund PR adds (proposals/*.md or rfps/<category>/*.md), exactly as in the PR head: abstract, specification, milestones, acceptance criteria, funding. A PR can add several files; pass path to pick one. Use after get_proposal when the details matter. Canton-specific.
List open Canton Dev Fund proposals waiting in the Needs Champion or Incoming columns of the Foundation's project board, i.e. with no champion confirmed there, oldest first, with what the proposal file and the PR text say about its champion. A proposal needs a champion, a sponsor from the Tech & Ops Committee, to move into review, and many stall without one. The bot labels needs-champion and champion-confirmed are deliberately NOT used as evidence: champion-confirmed is set from the PR text at filing and has been wrong. Evidence is the board column (champion assigned, Ready for Vote, Voting L…
List the Canton Foundation Dev Fund Requests for Proposals (RFPs) from the 2026-2028 roadmap: number, title, category, and how many Dev Fund proposals declare each one. Pass number to read one RFP in full: what the Foundation asks for, its stated appetite for grants, prior funded examples, and the proposals declaring it. RFP numbers are the ones proposals and labels use (RFP 18 is Integration into SDLCs). A proposal counts only if a label, its PR text, its title or its proposal file names the RFP, and most proposals do not, so a low count is not proof that an area is uncrowded. Canton-specifi…
Search ALL Canton Dev Fund text for words: proposal files, PR descriptions, every comment, formal review and inline review comment, ranked by relevance with a snippet around the match. Scope can be narrowed to comments, proposal_files or descriptions, and to one GitHub author. Use for "who said what about X", "which proposals mention Y", "did a reviewer object to Z". Default mode "words" is lexical (the words must appear, exact and exhaustive). Mode "meaning" searches the same text by meaning with embeddings plus words, so "did anyone worry about validator uptime" finds a comment that never s…
Changed the definition of "list_mailing_threads"
⟨9 unchanged words⟩ (lists.sync.global groups: cip-discuss, cip-vote, cip-announce,globalSyncForum,grants-discuss, validator-announce, tokenomics-announce, supervalidator-announce). Filter by ⟨31 unchanged words⟩
⟨23 unchanged words⟩ {"description":"Restrict to one of the87 indexed groups.","enum":["cip-discuss","cip-vote","cip-announce","globalSyncForum","grants-discuss","validator-announce","tokenomics-announce","supervalidator-announce ⟨62 unchanged words⟩
Changed the definition of "get_recent_changes"
Only numbers and dates differ: this server embeds live figures in the definition, so the text moves without the contract changing.
⟨35 unchanged words⟩ to return, newest first. Default 50, max200.500.","maximum":200500,"minimum":1,"type":"integer"}} ⟨2 unchanged words⟩
Recently observed → Live
Live → Recently observed
Certificate recorded, valid to 2026-12-05
Authorization not required
First tool surface recorded: 90 tools (server version 1.0.0)
Showing the latest 8 events. The API returns up to 500 and filters by kind: ?kind=tool_surface_changed