4,000+ servers built on vurb.ts
Vinkius
LlamaIndexFramework
LlamaIndex
TCE-SP (Audesp) MCP Server

Bring Transparency
to LlamaIndex

Learn how to connect TCE-SP (Audesp) to LlamaIndex and start using 3 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
List DespesasList MunicipiosList Receitas

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
TCE-SP (Audesp)

What is the TCE-SP (Audesp) MCP Server?

Connect to the TCE-SP Audesp system to audit and analyze public spending across municipalities in the state of São Paulo. This server provides direct access to the official transparency portal data.

What you can do

  • Municipality Lookup — List all cities under TCE-SP jurisdiction and retrieve their unique slugs for precise querying
  • Expense Analysis — Fetch detailed expense (despesas) records for any municipality, filtered by fiscal year and month
  • Revenue Tracking — Access revenue (receitas) data to monitor municipal collections and budget performance
  • Fiscal Auditing — Use AI to compare spending patterns and identify fiscal trends across different periods

How it works

  1. Subscribe to this server
  2. Enter your API access credentials or token
  3. Start querying public data from any MCP-compatible client like Claude or Cursor

Who is this for?

  • Journalists & Researchers — quickly extract fiscal data for investigative reporting without manual portal navigation
  • Public Managers — monitor municipal performance and compare budget execution against historical data
  • Citizens & Activists — promote transparency by easily accessing how public resources are being allocated

Built-in capabilities (3)

list_despesas

List expenses for a specific municipality, year, and month

list_municipios

List all municipalities under TCE-SP jurisdiction

list_receitas

List revenues for a specific municipality, year, and month

Why LlamaIndex?

LlamaIndex agents combine TCE-SP (Audesp) tool responses with indexed documents for comprehensive, grounded answers. Connect 3 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.

  • Data-first architecture: LlamaIndex agents combine TCE-SP (Audesp) tool responses with indexed documents for comprehensive, grounded answers

  • Query pipeline framework lets you chain TCE-SP (Audesp) tool calls with transformations, filters, and re-rankers in a typed pipeline

  • Multi-source reasoning: agents can query TCE-SP (Audesp), a vector store, and a SQL database in a single turn and synthesize results

  • Observability integrations show exactly what TCE-SP (Audesp) tools were called, what data was returned, and how it influenced the final answer

L
See it in action

TCE-SP (Audesp) in LlamaIndex

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

TCE-SP (Audesp) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect TCE-SP (Audesp) to LlamaIndex through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for TCE-SP (Audesp) in LlamaIndex

The TCE-SP (Audesp) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 3 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in LlamaIndex only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

TCE-SP (Audesp)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures TCE-SP (Audesp) for LlamaIndex

Every tool call from LlamaIndex to the TCE-SP (Audesp) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

How do I find the correct name (slug) for a specific city?

Use the list_municipios tool. It returns a complete list of all municipalities under TCE-SP jurisdiction with their respective slugs needed for expense and revenue queries.

02

Can I query data for any year and month?

Yes, using list_despesas or list_receitas, you can specify the exercicio (year) and mes (month, 1-12) to get precise historical data for a municipality.

03

What is the difference between list_despesas and list_receitas?

list_despesas focuses on how the municipality spent its budget (expenses), while list_receitas shows the income and collections (revenues) received by the city.

04

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.

05

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query TCE-SP (Audesp) tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.

06

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

07

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

Explore More MCP Servers

View all →