Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.mcparmory/ramp

OCI · GHCR.IO/MCPARMORY/RAMP:1.0.2 · 2 COMPONENTS

Manage expenses, corporate cards, accounts payable, and accounting integrations

−5 this week 47 Trust /100

Last scanned (8 hours ago)

Scores higher than 68% of OCI servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency6
  • Repository presence not verified: we could not reach the forge to check. This is a gap on our side, not a finding about the repository. View diagnostics → Unverified
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • License check failed: no license is declared. See how to fix → Fail
  • Actively maintained (last published 176 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 24416 tokens (~131/item across 186 items; 186 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety98
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 22 of 24 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_transfer" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 186 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (11)

  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (5)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  • Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  • Provenance in Provenance & TransparencyRepository presence not verified: we could not reach the forge to check. This is a gap on our side, not a finding about the repository.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 −5
    • Provenance: pass → unverified ▼ security
  • 1 Nov 26 +1
    • Stability: 0.97 → pass security
  • 31 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 24 Oct 26 +1
    • Stability: 0.97 → pass security
  • 23 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +1
    • Stability: 0.97 → pass security
  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed oci/ghcr.io/mcparmory/ramp:1.0.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 186 exposed · ~24,416 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
report_sync_results ~202

Report the results of a batch sync operation to Ramp, specifying which objects succeeded and which failed. An idempotency key ensures safe retry handling.

NameTypeReqDescription
failed_syncsarray–A list of objects that failed to sync, containing between 1 and 5000 items. Include this when reporting sync failures.
idempotency_keystringyesA unique identifier for this request, typically a randomly generated UUID. The server uses this to recognize and deduplicate retries of the same request.
successful_syncsarray–A list of objects that were successfully synced, containing between 1 and 5000 items. Include this when reporting sync successes.
sync_typestringyesThe category of objects being synced. Must be one of: BILL_PAYMENT_SYNC, BILL_SYNC, BROKERAGE_ORDER_SYNC, REIMBURSEMENT_SYNC, STATEMENT_CREDIT_SYNC, TRANSACTION_SYNC, TRANSFER_SYNC, or WALLET_TRANSFE…

No output schema declared.

No examples provided.

send_user_invite ~330

Trigger an asynchronous task to send a user invite via email. The invited user must accept the invite to complete onboarding and gain access to the system.

NameTypeReqDescription
department_idstring–UUID of the department to which the employee belongs.
direct_manager_idstring–UUID of the employee's direct manager.
emailstringyesThe employee's email address used for sending the invite and account access.
first_namestringyesThe employee's first name; limited to 255 characters.
idempotency_keystringyesA unique identifier generated by the client (preferably a UUID) to ensure idempotent request handling. The server uses this to recognize and deduplicate retries of the same request.
is_managerboolean–Whether the employee has managerial responsibilities and permissions.
last_namestringyesThe employee's last name; limited to 255 characters.
location_idstring–UUID of the location to which the employee is assigned. Locations are mapped to entities in a many-to-one relationship.
rolestringyesThe employee's role within the system. Valid roles are: AUDITOR, BUSINESS_ADMIN, BUSINESS_BOOKKEEPER, BUSINESS_OWNER, BUSINESS_USER, GUEST_USER, or IT_ADMIN. Note that BUSINESS_OWNER cannot be assign…
scheduled_deactivation_datestring–The date (in ISO 8601 format) when the user account will be automatically deactivated. For guest users, this defaults to 6 months from invite creation unless explicitly set to null. Cannot be set for…

No output schema declared.

No examples provided.

suspend_card ~106

Suspend a card to lock it from use. This creates an asynchronous task that prevents further transactions on the card; the suspension can be reverted later.

NameTypeReqDescription
card_idstringyesThe unique identifier of the card to suspend.
idempotency_keystringyesA unique identifier generated by the client (typically a UUID) to ensure idempotent behavior. The server uses this to recognize and deduplicate retried requests, preventing duplicate suspensions if t…

No output schema declared.

No examples provided.

suspend_spend_limit ~46

Suspend an active spend limit to temporarily halt enforcement of spending restrictions without deleting the limit configuration.

NameTypeReqDescription
spend_limit_idstringyesThe unique identifier of the spend limit to suspend.

No output schema declared.

No examples provided.

terminate_spend_limit ~97

Permanently terminate a spend limit by creating an asynchronous task. The operation is idempotent and can be safely retried.

NameTypeReqDescription
idempotency_keystringyesA unique value (typically a UUID) generated by the client to ensure idempotent request handling. The server uses this to recognize and deduplicate retries of the same request.
spend_limit_idstringyesThe unique identifier of the spend limit to terminate.

No output schema declared.

No examples provided.

unsuspend_card ~92

Initiates an asynchronous task to remove a card's suspension status, allowing it to be used for transactions again.

NameTypeReqDescription
card_idstringyesThe unique identifier of the card to unsuspend.
idempotency_keystringyesA unique identifier (typically a UUID) generated by the client to ensure idempotent request handling. The server uses this to recognize and deduplicate retries of the same request.

No output schema declared.

No examples provided.

unsuspend_spend_limit ~44

Reactivate a suspended spending limit, allowing it to enforce restrictions again.

NameTypeReqDescription
spend_limit_idstringyesThe unique identifier of the spend limit to unsuspend.

No output schema declared.

No examples provided.

update_accounting_connection ~85

Update the configuration settings for an accounting connection. This operation is restricted to API-based accounting connections and allows you to modify connection-specific settings.

NameTypeReqDescription
connection_idstringyesThe unique identifier of the accounting connection to update.
settingsobject–Configuration settings for the accounting connection. Only applicable to API-based connections; settings vary depending on the connection type and provider requirements.

No output schema declared.

No examples provided.

update_bill ~391

Update an approved bill with new financial details, line items, dates, or vendor information. Only bills with approved status can be modified.

NameTypeReqDescription
accounting_field_selectionsarray–List of accounting field selections used to code the bill for accounting purposes.
bill_idstringyesThe unique identifier of the bill to update.
due_atstring–The due date for payment, specified as a date in ISO 8601 format (YYYY-MM-DD).
entity_idstring–The UUID of the business entity associated with this bill.
inventory_line_itemsarray–List of inventory line items to attach to the bill. Providing this replaces all existing inventory line items.
invoice_numberstring–The vendor's invoice number, up to 20 characters.
issued_atstring–The date the bill was issued, specified as a date in ISO 8601 format (YYYY-MM-DD).
line_itemsarray–List of line items detailing charges on the bill. Providing this replaces all existing line items.
memostring–Internal memo or notes about the bill, up to 1000 characters.
posting_datestring–The date the bill is posted to the accounting system, specified as a date in ISO 8601 format (YYYY-MM-DD).
purchase_order_idsarray–List of purchase order identifiers to match against this bill. Providing this replaces all existing linked purchase orders.
remote_idstring–An external identifier that uniquely identifies this bill in the client's system.
vendor_contact_idstring–The UUID of the vendor contact associated with this bill. The contact must belong to the specified vendor.
vendor_idstring–The UUID of the vendor who issued this bill.
vendor_memostring–Memo or message to include for the vendor, up to 400 characters.

No output schema declared.

No examples provided.

update_card ~153

Update card properties including owner, display name, and spending restrictions. Allows modification of the associated business entity and notification settings.

NameTypeReqDescription
card_idstringyesThe unique identifier of the card to update.
entity_idstring–The UUID of the business entity to associate with this card. Use this to reassign the card to a different entity.
has_notifications_enabledboolean–Enable or disable notifications for this card.
new_user_idstring–The UUID of the user who will become the new owner of this card.
spending_restrictionsobject–Spending restrictions to apply to the card. Only include fields that need to be modified; unchanged restrictions do not need to be specified.

No output schema declared.

No examples provided.

update_custom_accounting_field ~107

Update properties of a custom accounting field in Ramp, such as its name or splittability configuration. Specify the field by its UUID and provide the properties you want to modify.

NameTypeReqDescription
field_idstringyesThe unique identifier (UUID) of the custom accounting field to update.
is_splittableboolean–Whether this custom field can be split across multiple line items or cost centers.
namestring–The display name for the custom accounting field.

No output schema declared.

No examples provided.

update_custom_field_option ~177

Update a custom accounting field option by modifying its code, name, visibility, or reactivation status. Only available for non-ERP integrated systems.

NameTypeReqDescription
codestring–The code identifier for this custom field option. You can provide an empty string to clear the code. Only available for non-ERP integrated systems.
field_option_idstringyesThe unique identifier (UUID format) of the custom field option to update.
reactivateboolean–Set to true to reactivate a previously deleted custom field option. Only available for non-ERP integrated systems.
valuestring–The display name of the custom field option. Only available for non-ERP integrated systems.
visibilitystring–Controls whether this option is visible or hidden in the UI. Must be either VISIBLE or HIDDEN.

No output schema declared.

No examples provided.

update_custom_field_option_partial ~178

Update a custom accounting field option by modifying its code, value, visibility, or reactivation status. Only available for non-ERP integrated systems.

NameTypeReqDescription
codestring–The code identifier for this custom field option. You can provide an empty string to clear the code. Only available for non-ERP integrated systems.
field_option_idstringyesThe unique identifier (UUID format) of the custom field option to update.
reactivateboolean–Set to true to reactivate a previously deleted custom field option. Only available for non-ERP integrated systems.
valuestring–The display name of the custom field option. Only available for non-ERP integrated systems.
visibilitystring–Controls whether this option is visible or hidden in the UI. Must be either VISIBLE or HIDDEN.

No output schema declared.

No examples provided.

update_custom_table_row_external_key ~109

Updates the external key identifier for a specific row in a custom table. This operation allows you to change how the row is referenced externally.

NameTypeReqDescription
custom_table_namestringyesThe name of the custom table containing the row to be updated.
new_external_keystringyesThe new external key value to assign to the row. This becomes the new external identifier for the row.
row_idstringyesThe unique identifier of the row whose external key should be changed.

No output schema declared.

No examples provided.

update_custom_table_rows ~111

Insert or update multiple rows in a custom table. Rows are identified by their existing keys, and all entries must contain the same set of column names with null values for columns that should not be modified.

NameTypeReqDescription
custom_table_namestringyesThe name of the custom table where rows will be inserted or updated.
dataarrayyesAn array of row objects to insert or update. All objects must have identical column names; use null to omit setting a value for a specific column in a row.

No output schema declared.

No examples provided.

update_department ~62

Update an existing department's information by its unique identifier. Allows modification of department details such as name.

NameTypeReqDescription
department_idstringyesThe unique identifier of the department to update, formatted as a UUID.
namestringyesThe new name for the department.

No output schema declared.

No examples provided.

update_draft_bill ~437

Update an existing draft bill with new details such as vendor information, line items, dates, and accounting settings. Changes are applied to the draft without posting to the accounting system.

NameTypeReqDescription
accounting_field_selectionsarray–List of accounting field options selected to categorize and code the bill for accounting purposes.
draft_bill_idstringyesThe unique identifier of the draft bill to update.
due_atstring–The due date for payment of the bill, specified as a calendar date.
enable_accounting_syncboolean–Set to false to prevent this bill from automatically syncing to your connected ERP system; defaults to true.
entity_idstring–The UUID of the business entity associated with this bill.
inventory_line_itemsarray–List of inventory line items to attach to the bill. Providing this list replaces all previously existing inventory line items.
invoice_currencystring–The currency code for the invoice amount, selected from the ISO 4217 standard currency list.
invoice_numberstring–The vendor's invoice number or reference identifier, up to 20 characters.
issued_atstring–The date the bill was issued by the vendor, specified as a calendar date.
line_itemsarray–List of line items detailing charges, quantities, and amounts on the bill. Providing this list replaces all previously existing line items.
memostring–Internal notes or comments about the bill, up to 1000 characters.
posting_datestring–The date the bill is posted or recorded in the accounting system, specified as a calendar date.
purchase_order_idsarray–List of purchase order identifiers to match and link with this bill. Providing this list replaces all previously linked purchase orders.
remote_idstring–An external identifier or reference number for this bill from your internal system or vendor portal.
vendor_contact_idstring–The UUID of the vendor contact person associated with this bill; the contact must belong to the specified vendor.
vendor_idstring–The UUID of the vendor issuing this bill.

No output schema declared.

No examples provided.

update_gl_account ~108

Update a general ledger account's name or code, or reactivate a previously deleted account.

NameTypeReqDescription
codestring–The new code for the general ledger account. Provide an empty string to clear the existing code.
gl_account_idstringyesThe unique identifier (UUID) of the general ledger account to update.
namestring–The new name for the general ledger account.
reactivateboolean–Set to true to reactivate a deleted general ledger account.

No output schema declared.

No examples provided.

update_inventory_item_field ~58

Update a specific accounting field for an inventory item. Use this to modify individual field values within an inventory item's accounting configuration.

NameTypeReqDescription
namestring–The name of the inventory item field to update. Specify which accounting field should be modified.

No output schema declared.

No examples provided.

update_inventory_item_option ~94

Update an inventory item option by modifying its name or reactivating a previously deleted option.

NameTypeReqDescription
namestring–The new name for the inventory item option.
option_idstringyesThe unique identifier of the inventory item option to update.
reactivateboolean–Reactivate a deleted inventory item option. When provided, this parameter must be set to true; false is not a valid value.

No output schema declared.

No examples provided.

update_location ~99

Update an existing location's details, including its name and associated business entity. Provide the location ID and the fields you want to update.

NameTypeReqDescription
entity_idstring–The UUID of the business entity this location belongs to. Provide this to reassign the location to a different entity.
location_idstringyesThe unique identifier of the location to update, formatted as a UUID.
namestringyesThe updated name for the location.

No output schema declared.

No examples provided.

update_native_table_rows ~103

Insert or update rows in a Native Ramp table. Specify the table by name and provide row data with consistent column sets across all entries.

NameTypeReqDescription
dataarrayyesAn array of row objects to insert or update. All objects must contain the same set of column names; use `null` values for columns that should not be set on specific rows.
native_table_namestringyesThe name of the Native Ramp table where rows will be inserted or updated.

No output schema declared.

No examples provided.

update_purchase_order ~178

Update an approved purchase order's spending dates and accounting field selections. Changes to accounting fields are applied atomically—all selections must be valid or the entire update will be rejected.

NameTypeReqDescription
accounting_field_selectionsarray–List of accounting field options to assign for coding the purchase order at the body level. Updates are applied in an all-or-nothing manner; typically only a single vendor accounting field is support…
purchase_order_idstringyesThe unique identifier of the purchase order to update, formatted as a UUID.
spend_end_datestring–The end date for spending on this purchase order, specified in ISO 8601 date format (YYYY-MM-DD).
spend_start_datestring–The start date for spending on this purchase order, specified in ISO 8601 date format (YYYY-MM-DD).

No output schema declared.

No examples provided.

update_purchase_order_line_item ~175

Update a single line item on an approved purchase order. Modify pricing, quantity, description, or accounting field assignments for the line item.

NameTypeReqDescription
accounting_field_selectionsarray–List of accounting field options to assign to this line item for coding purposes. Updates are applied atomically—all selections must be valid or the entire operation fails.
descriptionstring–Text description of the line item contents or purpose.
line_item_idstringyesThe unique identifier of the line item to update.
purchase_order_idstringyesThe unique identifier of the purchase order containing the line item.
unit_pricestring–Unit price for the line item. Accepts numeric values or numeric strings.
unit_quantityinteger–Quantity of units for the line item. Must be a positive integer.

No output schema declared.

No examples provided.

update_spend_limit ~348

Update an existing spend limit's configuration, including accounting rules, policy agent exemptions, sharing settings, spending restrictions, and program associations.

NameTypeReqDescription
accounting_rulesarray–Set or modify accounting rules that apply to all card transactions and reimbursements under this spend limit.
existing_expense_policy_agent_exemption_application_rulesstring–Controls how policy agent exemptions apply to existing transactions when is_exempt_from_policy_agent is enabled. Use APPLY_TO_ALL to retroactively exempt all existing transactions, or APPLY_TO_NONE t…
is_exempt_from_policy_agentboolean–When enabled, exempts this spend limit from policy agent review, preventing the policy agent from evaluating transactions against this limit.
is_shareableboolean–When enabled, allows this spend limit to be shared among multiple users.
new_user_idstring–Transfer ownership of this spend limit to a different user by providing their user ID.
permitted_spend_typesobject–Modify the types of spending permitted under this limit. When provided, all fields of permitted_spend_types must be included; partial updates are not supported.
spend_limit_idstringyesThe unique identifier of the spend limit to update.
spend_program_idstring–Link this spend limit to a spend program, which will override the limit's spending restrictions and permitted spend types with those defined in the program. Pass null to detach the current spend prog…
spending_restrictionsobject–Modify spending restrictions for this limit. When provided, the entire set of new restrictions must be specified, as they will completely replace all existing restrictions.

No output schema declared.

No examples provided.

update_spend_limit_partial ~350

Update configuration for a spend limit, including accounting rules, policy agent exemptions, sharing settings, spending restrictions, and program associations.

NameTypeReqDescription
accounting_rulesarray–Set or modify accounting rules that apply to all card transactions and reimbursements under this spend limit.
existing_expense_policy_agent_exemption_application_rulesstring–Controls how policy agent exemptions apply to existing transactions when is_exempt_from_policy_agent is enabled. Use APPLY_TO_ALL to retroactively exempt all existing transactions, or APPLY_TO_NONE t…
is_exempt_from_policy_agentboolean–When enabled, exempts this spend limit from policy agent review, preventing the policy agent from evaluating transactions against this limit.
is_shareableboolean–When enabled, allows this spend limit to be shared among multiple users.
new_user_idstring–Transfer ownership of this spend limit to a different user by providing their user ID.
permitted_spend_typesobject–Modify the types of spending permitted under this limit. When provided, all fields of permitted_spend_types must be included; partial updates are not supported.
spend_limit_idstringyesThe unique identifier of the spend limit to update.
spend_program_idstring–Link this spend limit to a spend program, which will override the limit's spending restrictions and permitted spend types with those defined in the program. Pass null to detach the current spend prog…
spending_restrictionsobject–Replace all spending restrictions for this limit with a new set. When provided, the entire set of restrictions must be specified; existing restrictions will be completely overridden.

No output schema declared.

No examples provided.

update_tax_code_field ~64

Update the name or other properties of a tax code accounting field. Use this operation to modify an existing tax code field's configuration.

NameTypeReqDescription
namestring–The new name for the tax code field. This identifier is used to reference the tax code in accounting operations.

No output schema declared.

No examples provided.

update_tax_code_option ~115

Update the name and associated tax rates for a specific tax code option. Changes to tax rate associations will replace all existing associations for this option.

NameTypeReqDescription
namestring–The display name for this tax code option.
option_idstringyesThe unique identifier of the tax code option to update.
tax_rate_idsarray–A list of external tax rate IDs (remote_id values) to associate with this tax code option. Providing this value will replace all existing tax rate associations. Order is not significant.

No output schema declared.

No examples provided.

update_tax_rate ~119

Update an existing tax rate's configuration, including its name, rate percentage, and associated GL account.

NameTypeReqDescription
accounting_gl_account_idstring–The Ramp ID of the GL account to associate with this tax rate. Must be a valid UUID format.
namestring–The display name for the tax rate.
ratestring–The tax rate percentage expressed as a decimal value (e.g., 0.10 for 10%).
tax_rate_idstringyesThe unique identifier of the tax rate to update.

No output schema declared.

No examples provided.

update_user ~294

Update user profile information including name, organizational hierarchy, role, and deactivation schedule. Supports partial updates of employee details.

NameTypeReqDescription
auto_promoteboolean–Automatically promote the user's manager to a manager role if they are not already one.
department_idstring–The unique identifier (UUID) of the department the employee belongs to.
direct_manager_idstring–The unique identifier (UUID) of the employee's direct manager.
first_namestring–The employee's first name. Must be at least 1 character long.
is_managerboolean–Whether the employee has manager-level permissions and responsibilities.
last_namestring–The employee's last name. Must be at least 1 character long.
location_idstring–The unique identifier (UUID) of the physical location where the employee is based.
rolestring–The employee's role within the organization. Valid roles include: AUDITOR, BUSINESS_ADMIN, BUSINESS_BOOKKEEPER, BUSINESS_OWNER, BUSINESS_USER, GUEST_USER, or IT_ADMIN.
scheduled_deactivation_datestring–The date (in ISO 8601 format) when the user account will be automatically deactivated. Set to null to remove a scheduled deactivation. Cannot be set for admin or owner roles.
user_idstringyesThe unique identifier of the user to update, formatted as a UUID.

No output schema declared.

No examples provided.

update_vendor ~218

Update vendor details including contact information, identifiers, and active status. Use this to modify an existing vendor's attributes in the system.

NameTypeReqDescription
accounting_vendor_remote_idstring–The remote identifier for this vendor in your accounting system. Provide either this or vendor_tracking_category_option_id, but not both.
addressobject–The vendor's physical address details.
countrystring–The country where the vendor is located.
descriptionstring–A descriptive name or label for the vendor.
external_vendor_idstring–A custom external identifier for the vendor that you define, independent of any accounting system identifiers.
is_activeboolean–Set to true to mark the vendor as active, or false to deactivate it.
vendor_idstringyesThe unique identifier of the vendor to update, formatted as a UUID.
vendor_tracking_category_option_idstring–The unique identifier of the vendor tracking category option, formatted as a UUID. Provide either this or accounting_vendor_remote_id, but not both.

No output schema declared.

No examples provided.

update_vendor_accounting ~110

Update vendor details including name and code, or reactivate a previously deleted vendor. Provide only the fields you want to modify.

NameTypeReqDescription
codestring–The vendor's code identifier. Provide an empty string to clear the existing code.
namestring–The display name of the vendor.
reactivateboolean–Set to true to restore a vendor that was previously deleted.
vendor_idstringyesThe unique identifier of the vendor to update, formatted as a UUID.

No output schema declared.

No examples provided.

upload_receipt ~145

Upload a receipt image and optionally link it to a transaction. If a transaction ID is provided, the receipt attaches directly to that transaction; otherwise, Ramp automatically matches the receipt to the most relevant transaction based on context.

NameTypeReqDescription
idempotency_keystringyesA unique identifier (UUID) that prevents duplicate uploads. Use a UUID to ensure idempotency across retries.
transaction_idstring–Optional UUID of the transaction to attach this receipt to. If omitted, Ramp will attempt to automatically match the receipt to the most relevant transaction.
user_idstringyesUUID of the user associated with this receipt. This affects the priority and accuracy of automatic transaction matching.

No output schema declared.

No examples provided.

upload_receipt_for_reimbursement ~139

Upload a receipt image for reimbursement processing. The receipt can be linked to an existing reimbursement or used to automatically create a new draft reimbursement via OCR analysis.

NameTypeReqDescription
idempotency_keystringyesA unique identifier (UUID) that prevents duplicate receipt uploads. Generate a new UUID for each upload request to ensure idempotency.
reimbursee_idstringyesThe UUID of the employee or user who will be reimbursed for this receipt.
reimbursement_idstring–The UUID of an existing reimbursement to attach this receipt to. If omitted, Ramp will automatically create a new draft reimbursement by extracting receipt data via OCR.

No output schema declared.

No examples provided.

upload_tax_rates ~96

Upload a batch of tax rates to your Ramp account. All rates in the batch are processed together—if any rate is malformed or violates constraints, the entire upload is rejected. Ensure rates are properly formatted and don't already exist in your system.

NameTypeReqDescription
tax_ratesarrayyesA list of tax rates to upload, containing between 1 and 500 rates. Each rate must be properly formatted and not already exist in your Ramp account.

No output schema declared.

No examples provided.

upsert_matrix_table_rows ~107

Creates new rows or updates existing rows in a matrix table. Rows are identified by their external_key; matching keys update existing rows while new keys create new rows. Result values can be partially updated.

NameTypeReqDescription
dataarrayyesArray of row objects to create or update. Each row must include an external_key field to identify whether it should be created or updated. Order is not significant.
table_namestringyesThe name of the matrix table to upsert rows into.

No output schema declared.

No examples provided.

Install

How do I install the com.mcparmory/ramp MCP server?

com.mcparmory/ramp runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/ramp:1.0.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/mcparmory/ramp:1.0.2

# add to Claude Code
claude mcp add com-mcparmory-ramp -- docker run --rm -i ghcr.io/mcparmory/ramp:1.0.2
Common questions

What is the com.mcparmory/ramp MCP server?

com.mcparmory/ramp is an MCP server listed in the public MCP registry as com.mcparmory/ramp. Manage expenses, corporate cards, accounts payable, and accounting integrations. This page covers its container image (ghcr.io/mcparmory/ramp:1.0.2).

Is the com.mcparmory/ramp MCP server safe to use?

com.mcparmory/ramp scores 47 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.mcparmory/ramp MCP server expose?

com.mcparmory/ramp exposes 186 tools: list_gl_accounts, create_gl_accounts, get_gl_account, update_gl_account, delete_gl_account, and 181 more. Their descriptions and schemas cost roughly 24,416 tokens of context every time the server is loaded.

Is the com.mcparmory/ramp MCP server still maintained?

com.mcparmory/ramp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the com.mcparmory/ramp MCP server?

VerifyMCP ran 11 checks on com.mcparmory/ramp, covering Provenance, License, Maintenance, Security disclosure and 7 more. 5 items could not be completed, a gap on our side rather than a finding about com.mcparmory/ramp: Malware scan, Known CVEs, Install scripts, Dependency health and 1 more. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.