// MCP SERVER RECORD

Cursor Usage

Unverified
REPOofershap/cursor-usage
BRisk grademodest
Catalogue entry updated 8 days ago
Auth postureNot probedno remote endpoint probed yet
Tools171 Write · 16 Read
Worst categoryWritegrade tracks the peak, not the average
Capability mix
Write 1Read 16
What it can reach
Ingests untrusted inputTouches secretsReaches networkRuns codeTouches filesChanges permissionsSends external commsPersistsDeletes dataMoves money
Tools 17
set_spend_limitWriteHighget_agent_editsReadLowget_billing_groupsReadMediumget_client_versionsReadLowget_commandsReadLow
View all 17 tools
get_daily_usageReadLowget_dauReadLowget_file_extensionsReadLowget_mcp_usageReadLowget_model_usageReadLowget_plansReadLowget_spendingReadLowget_tabsReadLowget_team_membersReadLowget_team_overviewReadLowget_usage_eventsReadLowget_user_deep_diveReadLow
Change history
No changes recorded since first scan. Watched servers surface a diff within the hour.
Recommended policy
set_spend_limitrate limit
Read-only toolsallow
Full policy breakdown with enforcement rules →
// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.