AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
MCP verified MIT Self-run

TinyMCP

mcp-qihoo360-tinymcp · by Qihoo360

A lightweight C++ SDK for implementing the MCP Server.

↗ Repository
— No reviews yet
0 installs
16 views
0.0% view→install

Install

$ agentstack add mcp-qihoo360-tinymcp

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of TinyMCP? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

TinyMCP

What is TinyMCP?

TinyMCP is a lightweight C++ SDK for implementing the MCP Server.

What is MCP?

MCP is an open protocol that standardizes how applications provide context to LLMs. Think of MCP like a USB-C port for AI applications. Just as USB-C provides a standardized way to connect your devices to various peripherals and accessories, MCP provides a standardized way to connect AI models to different data sources and tools. > Reference for details

TinyMCP supported system platforms

  • Windows
  • Linux
  • MacOS
  • Android
  • Other platforms that support standart c++...

Usage Guide

Please check the wiki for more information.

Dependencies

jsoncpp 1.9.5

MCP protocol version

MCP Specification 2024-11-05

Code structure brief

| directory | brief | | --- | --- | | Public | SDK public directory, used to store global type definitions, global constant resources, helper classes, etc. | | Message | Definition and implementation of the basic data structures of the MCP protocol, mainly including the implementation of protocol data such as standard requests, responses, and notifications that follow the JSON-RPC 2.0 protocol. | | Session | Definition and implementation of MCP protocol interaction sessions, mainly including the implementation of stateful sessions based on the C/S architecture and the maintenance of the complete MCP session lifecycle (initialization phase, running phase, and closing phase). | | Transport | Definition of data transmission channels between various endpoints based on the C/S architecture, which also includes an implementation of a default stdio transmission channel. | | Task | Definition and implementation of various MCP tasks, such as the three - way handshake and capability negotiation task during the initialization phase, and the processing tasks for major requests like Prompts, Resources, Tools, etc. Time - consuming tasks are executed asynchronously, while ordinary tasks are executed synchronously. | | Entity | Definition of various protocol entity classes for MCP, mainly including the base class of the Server following the Singleton pattern. |

Feature support brief

> Although not all features of the MCP protocol have been implemented, it is more than sufficient for you to implement your own MCP Server.

| Feature | Remarks | Essential Features | Supported or not | | --- | --- | --- | --- | | Base Protocol | Core JSON-RPC message types | Yes | Yes | | Lifecycle Management | Connection initialization, capability negotiation, and session control | Yes | Yes | | Transports | stdio | Yes | Yes | | Cancellation | Cancellation of in-progress requests through notification messages. | Yes | Yes | | Progress | Progress tracking for long-running operations through notification messages. | Yes | Yes | | Tools | Tools enable models to interact with external systems, such as querying databases, calling APIs, or performing computations. | Yes | Yes | | Resources | Resources allow servers to share data that provides context to language models, such as files, database schemas, or application-specific information. | Yes | Yes | | Pagination | Pagination allows servers to yield results in smaller chunks rather than all at once. | No | Yes | | Ping | Ping mechanism that allows either party to verify that their counterpart is still responsive and the connection is alive. | No | Yes | | Custom Notifications | JSON-RPC 2.0 notifications that are sent by an MCP Server or Client using custom method names, intended for transmitting arbitrary business data. | No | Yes | | Prompts | Prompts allow servers to provide structured messages and instructions for interacting with language models. | No | Yes | | Completion | A standardized way for servers to offer argument autocompletion suggestions for prompts and resource URIs. | No | Yes | | Logging | A standardized way for servers to send structured log messages to clients. | No | Yes | | Transports | HTTP with Server-Sent Events (SSE) | No | Not yet |

LICENSE

TinyMCP is licensed under the MIT License - see the LICENSE file for details.

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Integrations