Vero

Created By
kpi-zonea year ago
Overview

what is Vero?

Vero is a project designed to facilitate the management and visualization of key performance indicators (KPIs) using Cube.js and MCP server technology.

how to use Vero?

To use Vero, clone the repository from GitHub, set up the Cube.js server, and configure your data sources to start visualizing your KPIs.

key features of Vero?

  • Integration with Cube.js for powerful data analytics.
  • Customizable dashboards for KPI visualization.
  • Support for multiple data sources and formats.

use cases of Vero?

  1. Tracking business performance metrics in real-time.
  2. Visualizing sales data to identify trends and insights.
  3. Creating custom reports for stakeholders.

FAQ from Vero?

  • What technologies does Vero use?

Vero utilizes Cube.js and MCP server for data management and visualization.

  • Is Vero open source?

Yes! Vero is released under the GPL-3.0 license and is available on GitHub.

  • Can I contribute to Vero?

Absolutely! Contributions are welcome, and you can submit pull requests on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kpi-zone
Star
0
Language
Python
License
GPL-3.0 license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
MDMagic MCP Server
@MDMagic-MCP

Convert Markdown to DOCX, PDF, and HTML using your own Word templates — your letterhead, your branding, your fonts. Plus 15 designer-built templates for when you don't have your own. MDMagic plugs straight into Claude, Cursor, VS Code, and any MCP-compatible AI assistant, giving them direct access to a professional document conversion pipeline - and, more importantly, *your* templates. ✨ Use your own Word templates Upload your existing letterhead, stationery, brand guidelines, contract shells, proposal templates — anything you already use in Microsoft Word. Once uploaded, your AI assistant can convert any Markdown directly into a polished document carrying *your* logo, fonts, colours, footers, page numbers, watermarks, and signature blocks. The output looks like it came from your design team, not from a generic AI export. 🎨 Or pick from 15 designer-built templates Don't have a Word template ready? MDMagic ships with 15 professionally designed templates across four categories: • Business — Executive Platinum, Financial Blue, Premium Bronze, Professional Azure, Business Purple • Creative — Designer Indigo, Artistic Aqua, Sunset Vibes, Sage Serenity, Minimalist Pro, Cheese Burger • Professional — Legal Burgundy, Modern Legal • Technical — Code Documentation, Deep Data Blue 🧰 Ten tools, designed for AI workflows • convert_document — Markdown → DOCX, PDF, HTML, or all three • validate_markdown — pre-flight syntax check before you spend credits • estimate_conversion_cost — know the cost before the conversion runs • recommend_template — describe the document, get the right template • list_all_templates / list_builtin_templates / list_custom_templates — full catalogue with category filters • get_template_details — confirm page sizes, orientations, variants • check_credit_balance — credits remaining, plan status, cost-aware AI behaviour • show_default_settings — honour the user's preferred page size and orientation 💸 Same credits, one balance Whether you convert via the MDMagic web app or your AI assistant, credits work the same way. Free-tier credits renew monthly. Paid plans and one-off top-ups available. The MCP refuses conversions when your balance is low — no surprise bills. 🚀 Five-minute setup Sign up at https://mdmagic.ai/account → grab your API key → paste a JSON snippet into your AI client's MCP config → restart. Done. The hosted endpoint at https://api.mdmagic.ai/mcp is also available for clients that don't run local processes. Built for serious documents. Designed for AI assistants. Trusted with your brand.

15 hours ago
Nordic Data

2 days ago
Agent News

8 hours ago
Deepdive

6 hours ago
Polymarket Intel
@aemery13

An MCP server and REST API that classifies Polymarket wallets as human or bot, scores their trading edge from 0–10, and streams their current open positions. Built for AI agents on copy-trading and signal-following stacks. # Use it from any MCP client (Claude Desktop, Cursor, etc.) pip install polymarket-intel-mcp polymarket-intel-mcp # Or call the hosted REST API directly curl https://polymarket-intel-production.up.railway.app/wallet/0xf1528f12e645462c344799b62b1b421a6a4c64aa How this fits with other Polymarket MCP servers There are several MCP servers covering Polymarket, each at a different layer: Server What it does When to use it polymarket-intel (this) Wallet intelligence — classify human vs bot, score trading edge, read open positions Deciding whose signals to follow graph-polymarket-mcp Market data via The Graph subgraphs (20 tools, 8 subgraphs) Reading raw on-chain market data whitmorelabs/polymarket-mcp Slippage, liquidity, arbitrage, price feeds Pricing your own trades joinQuantish/polymarket Self-hosted trading agent Running an autonomous bot These complement each other. A copy-trading agent would use polymarket-intel to filter wallets worth following, then graph-polymarket-mcp to read the markets those wallets are betting on, then whitmorelabs/polymarket-mcp to size its own entries. What it answers "Is this trader a human or a bot?" — score_polymarket_wallet(wallet_address) → returns classification ∈ {human, bot, insufficient_data} plus a confidence score and reason codes. "Do they actually have an edge?" — edge_score from 0–10, gated on net realised PnL so distributed-but-losing wallets don't get false positives. "What are they betting on right now?" — get_open_positions(wallet_address) returns live positions sorted by size, refreshed every 30s. "How has their edge changed over time?" — /wallet/{address}/history returns the score time series from the daily snapshots. Why this exists The Polymarket leaderboard is misleading. It includes unrealised PnL marked-to-current-price, so the names at the top are dominated by bots running structural arb plus a few wallets sitting on huge open positions that may never resolve in their favour. Agents that copy-trade naively from the leaderboard get burned. This service runs every leaderboard wallet through behavioural fingerprinting (focus ratio, holding period, timing regularity, category concentration) plus PnL reconstruction from raw activity, and only surfaces traders that look like genuine humans with a real edge. The dataset grows more valuable over time — every day the snapshot job runs, historical signals accumulate. Wallets that have been consistently above edge 7 for 90 days are a stronger signal than any single point-in-time score. Distributed as both a REST API and an MCP server Surface Use case Setup MCP server Agent that needs tool-style access pip install polymarket-intel-mcp REST API Custom HTTP integration, dashboards curl https://polymarket-intel-production.up.railway.app/... Hosted MCP Agent on any MCP-compatible client Add https://polymarket-intel-production.up.railway.app/mcp to client config Architecture ┌──────────────────────────────────────────────┐ │ core/ │ │ client.py — Polymarket data API client │ │ signals.py — pure signal calculators │ │ scorer.py — classifier + edge score │ │ models.py — Pydantic response schemas │ ├──────────────────────────────────────────────┤ │ db/ │ │ schema.sql — Postgres tables + indexes │ │ repository.py — Repository protocol + │ │ InMemoryRepository │ │ supabase_repo.py — Supabase impl │ │ converters.py — ScoreResult ↔ records │ ├──────────────────────────────────────────────┤ │ api/main.py — FastAPI HTTP server │ │ mcp_server/ — MCP server (stdio) │ │ scripts/ │ │ analyze_wallet.py — CLI │ │ snapshot_job.py — daily cron entry │ │ tests/ │ └──────────────────────────────────────────────┘ Core has no idea persistence exists. The API and snapshot job depend on the Repository protocol — Supabase in production, in-memory in tests and when env vars are unset. This is what makes the suite run without a database and what lets you swap Supabase for Neon, RDS, or anything else later by adding one file.

2 days ago