LeashIndex Get the report

Index / storage

Untax

io-untax-untax declares 81 capabilities across 81 tools, with 3 critical issues. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.

96/100 exposureHigh exposure

Manifest recorded 2026-11-08 from tools/list on https://untax.io/api/v1/mcp, published in the official MCP registry as io.untax/untax 0.4.2. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 81 tools

81 of 81 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 3 of 81 tools

3 tools are classified as irreversible and declare no limit.

critical · uncapped-spend · 1 of 81 tools

1 tool is classified as moving money and declares no dollar limit. A cap on the number of payments does not bound their amount.

high · no-expiry · All 81 tools

81 of 81 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 81 tools

81 of 81 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 29 of 81 tools

29 tools can modify data and declare no limit.

low · uncapped-read · 49 of 81 tools

49 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
check_eligibilityread inferred
join_waitlistsend inferred
get_waitlist_analyticsread inferred
lookup_property_taxread inferred
get_property_assessmentread inferred
audit_property_taxwrite assumed
recheck_property_opportunitieswrite assumed
suggest_addressesread inferred
get_appeal_lifecycleread inferred
get_condition_evidence_catalogread inferred
suggest_property_condition_defectswrite assumed
quote_address_changeread inferred
check_portfolio_address_statusread inferred
get_microtransactions_catalogread inferred
check_delinquent_taxesread inferred
audit_disabled_veteran_reliefread declared
audit_square_footage_correctionwrite assumed
audit_commercial_reclassificationwrite assumed
get_hamilton_roll_analyticsread inferred
get_knox_roll_analyticsread inferred
get_roll_analyticsread inferred
analyze_parcel_reappraisal_surgeread inferred
audit_disabled_homeowner_reliefwrite assumed
discover_related_propertiesread declared
audit_surviving_spouse_vet_reliefwrite assumed
audit_senior_tax_freezeread inferred
get_representation_rulesread inferred
get_jurisdiction_exemption_profileread inferred
audit_scra_interest_capwrite assumed
verify_va_disability_exemptionread inferred
generate_sf180_requestwrite inferred
parse_va_benefit_letterwrite assumed
parse_scra_dmdc_certificateread inferred
audit_portfolio_batchwrite assumed
stage_portfolio_selectionwrite assumed
curate_portfolio_selectionwrite assumed
audit_fema_flood_hazardwrite assumed
audit_noaa_storm_swathswrite assumed
forecast_truth_in_taxation_bill_shockwrite assumed
audit_property_transferswrite inferred
audit_municipal_permitswrite assumed
audit_parcel_topographywrite assumed
audit_parcel_blight_citationswrite assumed
audit_parcel_soil_capabilitywrite assumed
audit_veteran_shieldread declared
generate_veteran_packetread declared
generate_vso_referralsend inferred
run_veteran_pilot_flowread declared
lookup_va_ogc_vsoread inferred
check_veteran_reliefread declared
audit_microtransactionread declared
audit_va_award_document_with_jevwrite assumed
audit_veteran_sah_ada_exclusionwrite assumed
audit_veteran_living_trust_preservationwrite assumed
audit_combat_deployment_abatementread inferred
audit_surviving_spouse_portabilitywrite inferred
audit_county_dd214_recordingwrite assumed
audit_disabled_veteran_wheel_taxwrite assumed
audit_va_funding_fee_refundpay inferred
audit_retroactive_tax_recoverywrite assumed
get_owner_workspaceread declared
get_owner_review_detailsread declared
get_property_model_readinessread inferred
simulate_property_modelread inferred
gisdb_search_catalogread inferred
gisdb_get_metadataread inferred
gisdb_request_sampleread declared
gisdb_calculate_ground_scaleread declared
gisdb_quote_enterpriseread declared
gisdb_create_checkoutread declared
gisdb_redeem_downloadread declared
gisdb_query_noticesread declared
gisdb_get_notice_dossierread declared
gisdb_export_distress_feedread declared
gisdb_get_stacked_leadsread declared
gisdb_get_cash_buyersread declared
gisdb_download_sample_bundleread declared
gisdb_subscribe_lead_feedread declared
start_tax_sandboxwrite inferred
get_tax_sandbox_orderread declared
complete_tax_sandbox_orderread inferred

Record history

Earlier records for this server. A correction is added here, never written over the record it corrects.

RecordedExposureSource
2026-10-2847 tools/list on https://untax.io/api/v1/mcp, published in the official MCP registry as io.untax/untax 0.4.2
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.