MPC Tally API Server

Created By
crazyrabbitLTCa year ago
A Model Context Protocol (MCP) server that enables AI agents to interact with the Tally API, providing access to DAO governance data, proposals, and metadata. Built with TypeScript and GraphQL, it offers a secure and efficient way to fetch and sort DAO information through standardized MCP functions.
Overview

what is MPC Tally API Server?

MPC Tally API Server is a Model Context Protocol (MCP) server that enables AI agents to interact with the Tally API, providing access to DAO governance data, proposals, and metadata.

how to use MPC Tally API Server?

To use the MPC Tally API Server, clone the repository, install dependencies, configure your API key, and run the server using the provided commands.

key features of MPC Tally API Server?

  • List DAOs sorted by popularity or exploration status
  • Fetch comprehensive DAO metadata including social links and governance information
  • Pagination support for handling large result sets
  • Built with TypeScript and GraphQL
  • Full test coverage with Bun's test runner

use cases of MPC Tally API Server?

  1. Fetching and displaying DAO governance data for analysis.
  2. Integrating DAO information into AI applications.
  3. Supporting decentralized governance through accessible metadata.

FAQ from MPC Tally API Server?

  • What is the purpose of the MPC Tally API Server?

It allows AI agents to fetch and interact with DAO governance data efficiently.

  • How do I secure my API key?

Keep your API key secure by not committing it to version control and using environment variables for configuration.

  • Can I customize the sorting of DAOs?

Yes! You can sort DAOs by various criteria such as popularity or exploration status.

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

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago