time-mcp

Created By
suryawanshishantanu6a year ago
MCP Server which returns current timestamp with streamlit app
Overview

what is time-mcp?

Time-mcp is a minimal agentic AI system designed to answer time-related and general questions using a tool-augmented LLM pipeline. It provides the current timestamp through a Flask API and features a Streamlit UI for user interaction.

how to use time-mcp?

To use time-mcp, clone the repository, install the dependencies, set your OpenRouter API key, and run the Flask API, MCP Agent Server, and Streamlit UI in separate terminals. You can then interact with the AI agent through the Streamlit interface.

key features of time-mcp?

  • Flask API for providing the current timestamp.
  • MCP Agent Server for detecting user intent and interacting with an LLM.
  • Streamlit UI for a simple chat interface with the AI agent.

use cases of time-mcp?

  1. Answering questions about the current time.
  2. Providing general information through natural language responses.
  3. Extending functionality by adding more tools to the MCP Agent.

FAQ from time-mcp?

  • Can time-mcp answer any question?

Yes, it can answer time-related questions and general inquiries using the LLM.

  • How do I set up time-mcp?

Follow the setup instructions in the documentation to clone the repo, install dependencies, and run the servers.

  • Is time-mcp customizable?

Yes, you can add more tools and improve intent detection by modifying the MCPAgent class.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
suryawanshishantanu6
Star
0
Language
Python
License
-

Recommend Servers

View All
Voyei

6 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.

16 hours ago