> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/api-documentation/api-reference/api--vibesec/types/objects/mcp-reputation-finding.md).

# mcpReputationFinding

### Examples

```graphql
type McpReputationFinding {
  id: String!
  ruleId: String!
  version: String
  title: String!
  severity: McpSeverity!
  category: String!
  description: String
  message: String
  file: String
  line: Int
  snippet: String
  sourceUrl: String
  usersExposed: Int
}
```

### Fields

| Field                                                                                                | Description                                                                                                                                | Supported fields |
| ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ---------------- |
| id `String!`                                                                                         | TNT finding id                                                                                                                             |                  |
| ruleId `String!`                                                                                     | TNT rule id that produced the finding                                                                                                      |                  |
| version `String`                                                                                     | Scanned package version the finding belongs to                                                                                             |                  |
| title `String!`                                                                                      | Rule label from the TNT rule catalog; falls back to the rule id                                                                            |                  |
| severity [`McpSeverity!`](/api-documentation/api-reference/api--vibesec/types/enums/mcp-severity.md) | Severity of the finding                                                                                                                    |                  |
| category `String!`                                                                                   | Rule category from the TNT rule catalog; unknown when the rule is missing                                                                  |                  |
| description `String`                                                                                 | What the rule observed, from the TNT rule catalog; falls back to the finding message                                                       |                  |
| message `String`                                                                                     | Finding-specific TNT message                                                                                                               |                  |
| file `String`                                                                                        | File the finding matched in                                                                                                                |                  |
| line `Int`                                                                                           | Line the finding matched on                                                                                                                |                  |
| snippet `String`                                                                                     | Code around the match (up to 4000 chars) from the scanned package; untrusted text                                                          |                  |
| sourceUrl `String`                                                                                   | Link to the exact file (and line when known) in the scanned version                                                                        |                  |
| usersExposed `Int`                                                                                   | Users whose current version (the one their latest call ran) is the affected version (npx servers only); null when versions are not tracked |                  |

### References

#### Fields with this object:

* [{} McpServerFindingsResponse.findings](/api-documentation/api-reference/api--vibesec/types/objects/mcp-server-findings-response.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ox.security/api-documentation/api-reference/api--vibesec/types/objects/mcp-reputation-finding.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.