@viberaven/mcp 1.7.7 → 1.7.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/lib/cli-runner.js +1 -1
- package/dist/server.js +290 -6
- package/dist/tools/index.js +289 -5
- package/package.json +1 -1
package/dist/lib/cli-runner.js
CHANGED
|
@@ -554,7 +554,7 @@ function mcpVersion() {
|
|
|
554
554
|
} catch {
|
|
555
555
|
}
|
|
556
556
|
}
|
|
557
|
-
found ??= true ? "1.7.
|
|
557
|
+
found ??= true ? "1.7.9" : void 0;
|
|
558
558
|
if (!found || !PLAIN_VERSION.test(found)) {
|
|
559
559
|
throw new Error(`Could not read a valid ${MCP_PACKAGE} version (got ${JSON.stringify(found)}), so the matching ${CLI_PACKAGE} cannot be pinned.`);
|
|
560
560
|
}
|
package/dist/server.js
CHANGED
|
@@ -575,11 +575,11 @@ var registry_generated_default = {
|
|
|
575
575
|
|
|
576
576
|
// ../providers/recent-changes.generated.mjs
|
|
577
577
|
var recent_changes_generated_default = {
|
|
578
|
-
"hash": "
|
|
578
|
+
"hash": "9055e719b6e6f6e4cd6e55c44af1b43dbbfda3d1fd273dd19e3d74385cf2803d",
|
|
579
579
|
"pack": {
|
|
580
580
|
"schemaVersion": 1,
|
|
581
|
-
"packVersion": "1.
|
|
582
|
-
"reviewedAt": "2026-
|
|
581
|
+
"packVersion": "1.3.0",
|
|
582
|
+
"reviewedAt": "2026-11-05",
|
|
583
583
|
"dateConvention": "effective = provider-stated date; announced = publication/release date; verified = checked date only, not rollout.",
|
|
584
584
|
"limits": [
|
|
585
585
|
"Guidance only; repository and live provider state remain not_checked.",
|
|
@@ -684,6 +684,81 @@ var recent_changes_generated_default = {
|
|
|
684
684
|
"id": "supabase-key-migration",
|
|
685
685
|
"url": "https://supabase.com/docs/guides/getting-started/migrating-to-new-api-keys",
|
|
686
686
|
"notes": "Create new keys alongside legacy; replace frontend anon with publishable and backend service_role with secret. Check components then disable legacy keys. Grant/RLS behavior retained, and key switch doesn't fix access policy."
|
|
687
|
+
},
|
|
688
|
+
{
|
|
689
|
+
"id": "next-security-oct-2026",
|
|
690
|
+
"url": "https://nextjs.org/blog/nextjs-security-update-october-14-2026",
|
|
691
|
+
"notes": "Dated October 14, 2026. Out-of-band release fixing two critical remote code execution issues (Image Optimization with SVG; use cache returning typed arrays) and a high-severity Server Actions denial of service. Fixed in next 16.4.1 and 15.5.28."
|
|
692
|
+
},
|
|
693
|
+
{
|
|
694
|
+
"id": "stripe-endive-checkout",
|
|
695
|
+
"url": "https://docs.stripe.com/changelog/endive/2026-09-30/remove-payment-method-types-checkout-sessions",
|
|
696
|
+
"notes": "API version 2026-09-30.endive removes the writable payment_method_types parameter from Checkout Session create; requests that send it fail with payment_method_types_no_longer_supported."
|
|
697
|
+
},
|
|
698
|
+
{
|
|
699
|
+
"id": "stripe-node-endive-pin",
|
|
700
|
+
"url": "https://raw.githubusercontent.com/stripe/stripe-node/master/CHANGELOG.md",
|
|
701
|
+
"notes": "stripe-node 23.0.0 (2026-09-30) pins API version 2026-09-30.endive, so a new install of the stripe package sends Endive requests unless apiVersion says otherwise."
|
|
702
|
+
},
|
|
703
|
+
{
|
|
704
|
+
"id": "openai-deprecations",
|
|
705
|
+
"url": "https://developers.openai.com/api/docs/deprecations",
|
|
706
|
+
"notes": "Shutdowns: legacy GPT snapshots on October 23, 2026 (gpt-3.5-turbo, gpt-4, gpt-4-turbo, o1, o3-mini, o4-mini, gpt-4.1-nano and others); GPT-5 and o3 snapshots on December 11, 2026; dated GPT-4o, GPT-4o mini and GPT-4.1 snapshots on January 14, 2027. Each row names a replacement."
|
|
707
|
+
},
|
|
708
|
+
{
|
|
709
|
+
"id": "lovable-changelog-models",
|
|
710
|
+
"url": "https://docs.lovable.dev/changelog",
|
|
711
|
+
"notes": "Lovable AI retired google/gemini-2.5-pro, -flash and -flash-lite on October 20, 2026 (requests rerouted); google/gemini-3.6-flash stops working November 19, 2026 and google/gemini-3.7-flash January 28, 2027; replacement google/gemini-3.8-flash."
|
|
712
|
+
},
|
|
713
|
+
{
|
|
714
|
+
"id": "anthropic-model-deprecations",
|
|
715
|
+
"url": "https://platform.claude.com/docs/en/about-claude/model-deprecations",
|
|
716
|
+
"notes": "claude-sonnet-4-5-20250929 retires on the Claude API on November 30, 2026 (replacement claude-sonnet-5-5). Earlier retirements include the claude-3-5-sonnet models, claude-3-7-sonnet-20250219, claude-3-5-haiku-20241022, claude-3-haiku-20240307 and the Claude 4 and 4.1 Opus and Sonnet snapshots. Bedrock and Vertex follow their own schedules."
|
|
717
|
+
},
|
|
718
|
+
{
|
|
719
|
+
"id": "supabase-claude-issued-mcp-auth-post",
|
|
720
|
+
"url": "https://supabase.com/blog/claude-issued-enterprise-managed-auth-for-mcp",
|
|
721
|
+
"notes": "Published November 3, 2026. Claude can issue the ID-JAG identity assertion for the Supabase MCP server when the IdP does not support the MCP Enterprise-Managed Authorization extension. Supabase side generally available to Team and Enterprise organizations with SSO; Claude auto-connect is a beta for Claude Team and Enterprise. Disabling a member in the IdP no longer cuts off access; tokens already issued stay valid until they expire."
|
|
722
|
+
},
|
|
723
|
+
{
|
|
724
|
+
"id": "supabase-enterprise-mcp-authorization",
|
|
725
|
+
"url": "https://supabase.com/docs/guides/platform/sso/enterprise-mcp-authorization",
|
|
726
|
+
"notes": "Setup guide, section Use Claude as the ID-JAG issuer. Supabase trusts one issuer URL per SSO provider, so saving the Claude URL makes Supabase reject every ID-JAG the IdP issues; each issuer URL serves one Supabase organization; emails must match (case-insensitive, no aliases or plus-addresses); under SCIM, Claude removes members only when the directory deletes them. No dates on the page."
|
|
727
|
+
},
|
|
728
|
+
{
|
|
729
|
+
"id": "next-security-2026-11-03-source",
|
|
730
|
+
"url": "https://nextjs.org/blog/november-2026-security-release",
|
|
731
|
+
"notes": "Read official announcement on 2026-11-05. Publication date and feature constraints verified; no provider or runtime check."
|
|
732
|
+
},
|
|
733
|
+
{
|
|
734
|
+
"id": "supabase-cli-v3-local-default-source",
|
|
735
|
+
"url": "https://supabase.com/changelog/supabase-cli-v3",
|
|
736
|
+
"notes": "Read official announcement on 2026-11-05. Publication date and feature constraints verified; no provider or runtime check."
|
|
737
|
+
},
|
|
738
|
+
{
|
|
739
|
+
"id": "supabase-cli-v3-migration-guide",
|
|
740
|
+
"url": "https://supabase.com/docs/guides/local-development/cli/migrating-to-v3",
|
|
741
|
+
"notes": "Migration guide updated November 3, 2026. Confirms local targets, hosted consent, removed inbucket sections, config precedence and auth.sms.enable_confirmations behavior. Guide update and default-install announcement dates are distinct."
|
|
742
|
+
},
|
|
743
|
+
{
|
|
744
|
+
"id": "vercel-security-review-beta-source",
|
|
745
|
+
"url": "https://vercel.com/changelog/vercel-security-review-public-beta",
|
|
746
|
+
"notes": "Read official announcement on 2026-11-05. Publication date and feature constraints verified; no provider or runtime check."
|
|
747
|
+
},
|
|
748
|
+
{
|
|
749
|
+
"id": "vercel-cli-doctor-source",
|
|
750
|
+
"url": "https://vercel.com/changelog/vercel-cli-now-diagnoses-setup-problems-with-vercel-doctor",
|
|
751
|
+
"notes": "Read official announcement on 2026-11-05. Publication date and feature constraints verified; no provider or runtime check."
|
|
752
|
+
},
|
|
753
|
+
{
|
|
754
|
+
"id": "clerk-native-minimum-version-source",
|
|
755
|
+
"url": "https://clerk.com/changelog/2026-11-03-minimum-app-version",
|
|
756
|
+
"notes": "Read official announcement on 2026-11-05. Publication date and feature constraints verified; no provider or runtime check."
|
|
757
|
+
},
|
|
758
|
+
{
|
|
759
|
+
"id": "vercel-workflow-atomic-start-source",
|
|
760
|
+
"url": "https://vercel.com/changelog/atomic-start-hooks-in-the-workflow-sdk",
|
|
761
|
+
"notes": "Read official announcement on 2026-11-05. Publication date and feature constraints verified; no provider or runtime check."
|
|
687
762
|
}
|
|
688
763
|
],
|
|
689
764
|
"entries": [
|
|
@@ -816,6 +891,215 @@ var recent_changes_generated_default = {
|
|
|
816
891
|
"supabase-key-migration"
|
|
817
892
|
],
|
|
818
893
|
"limitations": "No key/account/provider inspection, rotation, or live request. Switching key formats does not fix missing grants or RLS policies."
|
|
894
|
+
},
|
|
895
|
+
{
|
|
896
|
+
"id": "next-security-2026-10-14",
|
|
897
|
+
"provider": "nextjs",
|
|
898
|
+
"date": "2026-10-14",
|
|
899
|
+
"dateKind": "announced",
|
|
900
|
+
"dateNote": "October announcement date. The November 3 follow-up is tracked separately as next-security-2026-11-03; October patch status does not clear November issues.",
|
|
901
|
+
"whatChanged": "Next.js fixed two critical remote code execution vulnerabilities (Image Optimization with SVG input, and use cache returning typed arrays) and a high-severity Server Actions denial of service. Affected: next 10.0.0 to 15.5.27 and 16.0.0 to 16.4.0.",
|
|
902
|
+
"errorText": null,
|
|
903
|
+
"errorTextKind": "not_documented",
|
|
904
|
+
"symptom": "No error: an unpatched app keeps working while exposed.",
|
|
905
|
+
"fix": "Upgrade next to 16.4.1 (16.x) or 15.5.28 (15.x and older lines), reinstall so the lockfile resolves the patched version, rebuild and redeploy. A caret range in package.json may already resolve to a patched version; the lockfile decides.",
|
|
906
|
+
"officialSource": "https://nextjs.org/blog/nextjs-security-update-october-14-2026",
|
|
907
|
+
"sourceIds": [
|
|
908
|
+
"next-security-oct-2026"
|
|
909
|
+
],
|
|
910
|
+
"limitations": "Version ranges come from the GitHub advisories linked by the post. A repo shows the declared range; only the lockfile or npm ls next shows the installed version. Whether Vercel-hosted deployments are shielded is not stated."
|
|
911
|
+
},
|
|
912
|
+
{
|
|
913
|
+
"id": "stripe-endive-payment-method-types",
|
|
914
|
+
"provider": "stripe",
|
|
915
|
+
"date": "2026-09-30",
|
|
916
|
+
"dateKind": "effective",
|
|
917
|
+
"dateNote": "Applies to requests on API version 2026-09-30.endive or later. stripe-node 23.0.0 pins that version, so a fresh npm install stripe gets it.",
|
|
918
|
+
"whatChanged": "API version Endive removes the writable payment_method_types parameter from Checkout Session create and from PaymentIntent and SetupIntent create, update and confirm. Requests that still send it fail.",
|
|
919
|
+
"errorText": "payment_method_types_no_longer_supported",
|
|
920
|
+
"errorTextKind": "official_documentation_example",
|
|
921
|
+
"errorCode": "payment_method_types_no_longer_supported",
|
|
922
|
+
"symptom": "Checkout or payment creation returns HTTP 400 after upgrading the stripe package.",
|
|
923
|
+
"fix": "Remove payment_method_types from those calls. Rely on dynamic payment methods set in the Dashboard, or use allowed_payment_method_types or excluded_payment_method_types. Test in test mode; reading payment_method_types from a response is unaffected.",
|
|
924
|
+
"officialSource": "https://docs.stripe.com/changelog/endive/2026-09-30/remove-payment-method-types-checkout-sessions",
|
|
925
|
+
"sourceIds": [
|
|
926
|
+
"stripe-endive-checkout",
|
|
927
|
+
"stripe-node-endive-pin"
|
|
928
|
+
],
|
|
929
|
+
"limitations": "A client built with an explicit pre-Endive apiVersion is not affected, and a raw REST call uses the account default version, which the repo does not show."
|
|
930
|
+
},
|
|
931
|
+
{
|
|
932
|
+
"id": "openai-model-shutdowns-2026",
|
|
933
|
+
"provider": "openai",
|
|
934
|
+
"date": "2026-12-11",
|
|
935
|
+
"dateKind": "effective",
|
|
936
|
+
"dateNote": "Three dates: legacy GPT snapshots shut down 2026-10-23; GPT-5 and o3 snapshots on 2026-12-11; dated GPT-4o, GPT-4o mini and GPT-4.1 snapshots on 2027-01-14.",
|
|
937
|
+
"whatChanged": "OpenAI removes these model IDs from the API: gpt-3.5-turbo, gpt-4, gpt-4-turbo, o1, o3-mini, o4-mini, gpt-4.1-nano and gpt-image-1 (2026-10-23); gpt-5, gpt-5-mini, gpt-5-nano, gpt-5-pro, o3 and o3-pro (2026-12-11); gpt-4o-2024-08-06, gpt-4o-2024-11-20, gpt-4o-mini-2024-07-18 and gpt-4.1-2025-04-14 (2027-01-14). Requests to a removed model fail.",
|
|
938
|
+
"errorText": null,
|
|
939
|
+
"errorTextKind": "not_documented",
|
|
940
|
+
"symptom": "An AI feature that worked starts failing with a model not found error after the shutdown date.",
|
|
941
|
+
"fix": "Replace each model ID with the replacement the deprecations page lists, then run the feature once and compare output and cost.",
|
|
942
|
+
"officialSource": "https://developers.openai.com/api/docs/deprecations",
|
|
943
|
+
"sourceIds": [
|
|
944
|
+
"openai-deprecations"
|
|
945
|
+
],
|
|
946
|
+
"limitations": "Azure OpenAI deployments and OpenRouter-style openai/... IDs follow other schedules. The bare aliases gpt-4o and gpt-4o-mini are not on the page."
|
|
947
|
+
},
|
|
948
|
+
{
|
|
949
|
+
"id": "lovable-ai-gemini-retirements",
|
|
950
|
+
"provider": "lovable",
|
|
951
|
+
"date": "2026-11-19",
|
|
952
|
+
"dateKind": "effective",
|
|
953
|
+
"dateNote": "Gemini 2.5 models were retired on 2026-10-20 with requests rerouted; google/gemini-3.6-flash stops on 2026-11-19 and google/gemini-3.7-flash on 2027-01-28.",
|
|
954
|
+
"whatChanged": "Lovable AI retired google/gemini-2.5-pro, google/gemini-2.5-flash and google/gemini-2.5-flash-lite (rerouted to newer models, which changes cost and answers). google/gemini-3.6-flash and google/gemini-3.7-flash stop working on their dates. The replacement is google/gemini-3.8-flash.",
|
|
955
|
+
"errorText": null,
|
|
956
|
+
"errorTextKind": "not_documented",
|
|
957
|
+
"symptom": "AI answers or cost change after 2026-10-20; requests to the 3.6 or 3.7 Flash model fail after their dates.",
|
|
958
|
+
"fix": "Change the model string to google/gemini-3.8-flash (or ask Lovable to), redeploy the edge function, and check one real request.",
|
|
959
|
+
"officialSource": "https://docs.lovable.dev/changelog",
|
|
960
|
+
"sourceIds": [
|
|
961
|
+
"lovable-changelog-models"
|
|
962
|
+
],
|
|
963
|
+
"limitations": "The same google/... strings sent through OpenRouter or another gateway follow that gateway, not Lovable."
|
|
964
|
+
},
|
|
965
|
+
{
|
|
966
|
+
"id": "anthropic-claude-model-retirements",
|
|
967
|
+
"provider": "anthropic",
|
|
968
|
+
"date": "2026-11-30",
|
|
969
|
+
"dateKind": "effective",
|
|
970
|
+
"dateNote": "claude-sonnet-4-5-20250929 retires on 2026-11-30 (deprecated 2026-09-30). Several older Claude models are already retired.",
|
|
971
|
+
"whatChanged": "Requests to a retired Claude model fail. claude-sonnet-4-5-20250929 retires on 2026-11-30 (replacement claude-sonnet-5-5). Already retired: the claude-3-5-sonnet models, claude-3-7-sonnet-20250219, claude-3-5-haiku-20241022, claude-3-haiku-20240307, claude-sonnet-4-20250514, claude-opus-4-20250514 and claude-opus-4-1-20250805.",
|
|
972
|
+
"errorText": null,
|
|
973
|
+
"errorTextKind": "not_documented",
|
|
974
|
+
"symptom": "An AI feature that worked starts failing after the retirement date.",
|
|
975
|
+
"fix": "Switch each model ID to the replacement on the deprecations page and test the output.",
|
|
976
|
+
"officialSource": "https://platform.claude.com/docs/en/about-claude/model-deprecations",
|
|
977
|
+
"sourceIds": [
|
|
978
|
+
"anthropic-model-deprecations"
|
|
979
|
+
],
|
|
980
|
+
"limitations": "Amazon Bedrock and Google Vertex AI model IDs follow those platforms. The undated alias claude-sonnet-4-5 is not in the table."
|
|
981
|
+
},
|
|
982
|
+
{
|
|
983
|
+
"id": "supabase-mcp-claude-issued-auth",
|
|
984
|
+
"provider": "supabase",
|
|
985
|
+
"date": "2026-11-03",
|
|
986
|
+
"dateKind": "announced",
|
|
987
|
+
"dateNote": "Supabase blog post date. The Supabase side is generally available to Team and Enterprise organizations with SSO; Claude's side (Claude-issued auth, auto-connect) is a beta for Claude Team and Enterprise.",
|
|
988
|
+
"whatChanged": "Enterprise-managed authorization for the Supabase MCP server no longer needs an IdP that supports the MCP extension: Claude can sign the ID-JAG identity assertion instead. A Claude admin copies Claude's per-organization issuer URL from Organization settings > Connectors > Supabase > Managed authorization, a Supabase owner or admin pastes it into SSO > Advanced settings > ID-JAG Issuer, and members in the chosen Claude roles then see Supabase connected with no sign-in or consent screen.",
|
|
989
|
+
"errorText": null,
|
|
990
|
+
"errorTextKind": "not_documented",
|
|
991
|
+
"errorCode": null,
|
|
992
|
+
"symptom": "After the Claude issuer URL is saved, Supabase rejects every ID-JAG the IdP issues, so other AI tools that use the IdP for managed authorization lose access until the IdP URL is restored. A member disabled only in the IdP keeps access.",
|
|
993
|
+
"fix": "Before saving the Claude issuer URL, list the tools that use the IdP's ID-JAG: Supabase trusts one issuer per SSO provider, and each issuer URL serves one Supabase organization. Members need the same email in Claude and Supabase (case-insensitive, no aliases or plus-addresses) and one SSO sign-in to Supabase. To offboard, remove the member from both the Supabase and the Claude organization; tokens already issued stay valid until they expire. Remove a former member from Supabase before reusing their email. Under SCIM, Claude removes members only when the directory deletes them, not when it suspends them.",
|
|
994
|
+
"officialSource": "https://supabase.com/blog/claude-issued-enterprise-managed-auth-for-mcp",
|
|
995
|
+
"sourceIds": [
|
|
996
|
+
"supabase-claude-issued-mcp-auth-post",
|
|
997
|
+
"supabase-enterprise-mcp-authorization"
|
|
998
|
+
],
|
|
999
|
+
"limitations": "Dashboard configuration only: repository files cannot show SSO, the issuer URL, organization membership or connector roles. Claude checks organization membership and the account email, not IdP sign-in, MFA or Supabase sign-in rules. Neither source gives a token lifetime."
|
|
1000
|
+
},
|
|
1001
|
+
{
|
|
1002
|
+
"id": "next-security-2026-11-03",
|
|
1003
|
+
"provider": "nextjs",
|
|
1004
|
+
"date": "2026-11-03",
|
|
1005
|
+
"symptom": "Depending on enabled features and hosting, an older release can disclose cached data or cookies, poison caches, or mishandle responses. Version alone does not prove exposure.",
|
|
1006
|
+
"fix": "Upgrade the installed/locked next dependency to 16.4.5 or 15.5.29 for its release line, rebuild and test. Read the individual advisory conditions for Cache Components, self-hosting, Edge routes and image backends.",
|
|
1007
|
+
"dateKind": "announced",
|
|
1008
|
+
"dateNote": "Official announcement publication date, not proof of rollout to this project.",
|
|
1009
|
+
"whatChanged": "Next.js released 16.4.5 and 15.5.29 for seven security issues involving cache isolation, self-hosted response handling, Edge cookie headers and image decoding.",
|
|
1010
|
+
"errorText": null,
|
|
1011
|
+
"errorTextKind": "not_documented",
|
|
1012
|
+
"officialSource": "https://nextjs.org/blog/november-2026-security-release",
|
|
1013
|
+
"sourceIds": [
|
|
1014
|
+
"next-security-2026-11-03-source"
|
|
1015
|
+
],
|
|
1016
|
+
"limitations": "A declaration is not an installed or deployed version. The notice does not establish universal exploitability; hosting and feature preconditions differ per issue."
|
|
1017
|
+
},
|
|
1018
|
+
{
|
|
1019
|
+
"id": "supabase-cli-v3-local-default",
|
|
1020
|
+
"provider": "supabase",
|
|
1021
|
+
"date": "2026-11-04",
|
|
1022
|
+
"symptom": "CLI automation may target local instead of hosted or stop for consent; old inbucket configuration prevents local commands from starting.",
|
|
1023
|
+
"fix": "Inspect installed CLI help and pin the intended version. Before upgrading automation, review every target: explicitly select --remote for intended hosted database work and deliberately authorize each hosted mutation before adding --yes. Rename [inbucket] to [local_smtp] and review environment overrides and pg-delta output.",
|
|
1024
|
+
"dateKind": "announced",
|
|
1025
|
+
"dateNote": "November 4 default-install announcement, distinct from the November 2 v3.0.0 release and November 3 migration-guide update. Not proof of rollout to this project.",
|
|
1026
|
+
"whatChanged": "Supabase CLI v3 is now the default install. Database commands target local by default; hosted mutations require consent, including --yes when unattended. Config precedence changes and [inbucket] becomes [local_smtp].",
|
|
1027
|
+
"errorText": null,
|
|
1028
|
+
"errorTextKind": "not_documented",
|
|
1029
|
+
"officialSource": "https://supabase.com/changelog/supabase-cli-v3",
|
|
1030
|
+
"sourceIds": [
|
|
1031
|
+
"supabase-cli-v3-local-default-source",
|
|
1032
|
+
"supabase-cli-v3-migration-guide"
|
|
1033
|
+
],
|
|
1034
|
+
"limitations": "CLI migration guidance only. Hosted projects do not change merely because v3 exists. No command or mutation was executed; a repo cannot establish which CLI a CI runner installs."
|
|
1035
|
+
},
|
|
1036
|
+
{
|
|
1037
|
+
"id": "vercel-security-review-beta",
|
|
1038
|
+
"provider": "vercel",
|
|
1039
|
+
"date": "2026-11-03",
|
|
1040
|
+
"symptom": "Informational capability announcement, not a breaking change or a finding that this repository is vulnerable.",
|
|
1041
|
+
"fix": "If the team is eligible, review Security Review configuration and inspect commit-specific findings in the dashboard. Proposed fixes still require review; this feed does not enable the service.",
|
|
1042
|
+
"dateKind": "announced",
|
|
1043
|
+
"dateNote": "Official announcement publication date, not proof of rollout to this project.",
|
|
1044
|
+
"whatChanged": "Vercel Security Review entered public beta for Pro and Enterprise teams. Once enabled, pushes to connected GitHub repositories trigger reviews; findings appear in the Vulnerabilities dashboard.",
|
|
1045
|
+
"errorText": null,
|
|
1046
|
+
"errorTextKind": "not_documented",
|
|
1047
|
+
"officialSource": "https://vercel.com/changelog/vercel-security-review-public-beta",
|
|
1048
|
+
"sourceIds": [
|
|
1049
|
+
"vercel-security-review-beta-source"
|
|
1050
|
+
],
|
|
1051
|
+
"limitations": "Repository config does not prove plan eligibility, enablement, a completed security review, or absence of vulnerabilities. No account or GitHub integration was changed."
|
|
1052
|
+
},
|
|
1053
|
+
{
|
|
1054
|
+
"id": "vercel-cli-doctor",
|
|
1055
|
+
"provider": "vercel",
|
|
1056
|
+
"date": "2026-11-03",
|
|
1057
|
+
"symptom": "Informational diagnostic option when an agent encounters a Vercel CLI setup problem; a repo signal is not evidence of such a problem.",
|
|
1058
|
+
"fix": "With a CLI version supporting it, run vercel doctor --json and inspect individual statuses before taking further action. Doctor does not log in, prompt, or link a project.",
|
|
1059
|
+
"dateKind": "announced",
|
|
1060
|
+
"dateNote": "Official announcement publication date, not proof of rollout to this project.",
|
|
1061
|
+
"whatChanged": "Vercel CLI adds doctor with structured JSON statuses and suggested commands for installation, identity/team, project linking, configuration and status incidents.",
|
|
1062
|
+
"errorText": null,
|
|
1063
|
+
"errorTextKind": "not_documented",
|
|
1064
|
+
"officialSource": "https://vercel.com/changelog/vercel-cli-now-diagnoses-setup-problems-with-vercel-doctor",
|
|
1065
|
+
"sourceIds": [
|
|
1066
|
+
"vercel-cli-doctor-source"
|
|
1067
|
+
],
|
|
1068
|
+
"limitations": "This matcher never invokes doctor or checks login, linking, team membership, incidents or installed global tooling. Suggested remedial commands require their own review."
|
|
1069
|
+
},
|
|
1070
|
+
{
|
|
1071
|
+
"id": "clerk-native-minimum-version",
|
|
1072
|
+
"provider": "clerk",
|
|
1073
|
+
"date": "2026-11-03",
|
|
1074
|
+
"symptom": "Users below an enabled minimum must update. Earlier SDKs may not show the update screen; older iOS SDKs can show an error.",
|
|
1075
|
+
"fix": "Release a compatible build before setting a minimum: Clerk iOS 1.7.0, Android 1.4.0 or @clerk/expo 4.15.0 or later, plus required platform setup. Review the Dashboard minimum separately.",
|
|
1076
|
+
"dateKind": "announced",
|
|
1077
|
+
"dateNote": "Official announcement publication date, not proof of rollout to this project.",
|
|
1078
|
+
"whatChanged": "Clerk adds Dashboard minimum-version enforcement for native apps. Compatible SDKs display an update screen while retaining sign-in state.",
|
|
1079
|
+
"errorText": null,
|
|
1080
|
+
"errorTextKind": "not_documented",
|
|
1081
|
+
"officialSource": "https://clerk.com/changelog/2026-11-03-minimum-app-version",
|
|
1082
|
+
"sourceIds": [
|
|
1083
|
+
"clerk-native-minimum-version-source"
|
|
1084
|
+
],
|
|
1085
|
+
"limitations": "The matcher recognizes Expo package usage only, not native Swift/Kotlin projects. Dependency presence does not establish the installed SDK, released build, store availability, or Dashboard configuration."
|
|
1086
|
+
},
|
|
1087
|
+
{
|
|
1088
|
+
"id": "vercel-workflow-atomic-start",
|
|
1089
|
+
"provider": "vercel",
|
|
1090
|
+
"date": "2026-11-04",
|
|
1091
|
+
"symptom": "Concurrent requests can start duplicate work when a hook lookup and run admission are separate operations.",
|
|
1092
|
+
"fix": "Review legacy getHookByToken followed by start. Use start with experimental_hook: { token } for atomic admission; handle HookConflictError and resumeHook to route a duplicate payload to the existing run. Verify application-specific concurrency behavior.",
|
|
1093
|
+
"dateKind": "announced",
|
|
1094
|
+
"dateNote": "Official announcement publication date, not proof of rollout to this project.",
|
|
1095
|
+
"whatChanged": "Workflow SDK can atomically claim a hook when admitting a run. The earlier lookup-then-start approach has a duplicate-start race.",
|
|
1096
|
+
"errorText": null,
|
|
1097
|
+
"errorTextKind": "not_documented",
|
|
1098
|
+
"officialSource": "https://vercel.com/changelog/atomic-start-hooks-in-the-workflow-sdk",
|
|
1099
|
+
"sourceIds": [
|
|
1100
|
+
"vercel-workflow-atomic-start-source"
|
|
1101
|
+
],
|
|
1102
|
+
"limitations": "Same-file calls are a review signal, not proof of a race. This feed does not install a Workflow SDK, execute workflows or prove application idempotency."
|
|
819
1103
|
}
|
|
820
1104
|
]
|
|
821
1105
|
}
|
|
@@ -1875,7 +2159,7 @@ async function boundedJson2(response2) {
|
|
|
1875
2159
|
}
|
|
1876
2160
|
|
|
1877
2161
|
// ../cli/src/version.ts
|
|
1878
|
-
var VERSION = "1.7.
|
|
2162
|
+
var VERSION = "1.7.9";
|
|
1879
2163
|
|
|
1880
2164
|
// ../cli/src/commands/account.ts
|
|
1881
2165
|
var loginNext = `npx -y viberaven@${VERSION} login --json`;
|
|
@@ -2220,7 +2504,7 @@ function mcpVersion() {
|
|
|
2220
2504
|
} catch {
|
|
2221
2505
|
}
|
|
2222
2506
|
}
|
|
2223
|
-
found ??= true ? "1.7.
|
|
2507
|
+
found ??= true ? "1.7.9" : void 0;
|
|
2224
2508
|
if (!found || !PLAIN_VERSION.test(found)) {
|
|
2225
2509
|
throw new Error(`Could not read a valid ${MCP_PACKAGE} version (got ${JSON.stringify(found)}), so the matching ${CLI_PACKAGE} cannot be pinned.`);
|
|
2226
2510
|
}
|
|
@@ -2488,7 +2772,7 @@ async function handleRequest(method, params) {
|
|
|
2488
2772
|
}
|
|
2489
2773
|
|
|
2490
2774
|
// src/server.ts
|
|
2491
|
-
var SERVER_INFO = { name: "viberaven-mcp", version: "1.7.
|
|
2775
|
+
var SERVER_INFO = { name: "viberaven-mcp", version: "1.7.9" };
|
|
2492
2776
|
var INSTRUCTIONS = [
|
|
2493
2777
|
"VibeRaven reads a repository and lists launch gaps for AI-built apps that deploy on Vercel and use Supabase.",
|
|
2494
2778
|
"Suggest one viberaven_check_readiness run before such an app launches or is handed off, after a Supabase migration or policy change,",
|
package/dist/tools/index.js
CHANGED
|
@@ -576,11 +576,11 @@ var registry_generated_default = {
|
|
|
576
576
|
|
|
577
577
|
// ../providers/recent-changes.generated.mjs
|
|
578
578
|
var recent_changes_generated_default = {
|
|
579
|
-
"hash": "
|
|
579
|
+
"hash": "9055e719b6e6f6e4cd6e55c44af1b43dbbfda3d1fd273dd19e3d74385cf2803d",
|
|
580
580
|
"pack": {
|
|
581
581
|
"schemaVersion": 1,
|
|
582
|
-
"packVersion": "1.
|
|
583
|
-
"reviewedAt": "2026-
|
|
582
|
+
"packVersion": "1.3.0",
|
|
583
|
+
"reviewedAt": "2026-11-05",
|
|
584
584
|
"dateConvention": "effective = provider-stated date; announced = publication/release date; verified = checked date only, not rollout.",
|
|
585
585
|
"limits": [
|
|
586
586
|
"Guidance only; repository and live provider state remain not_checked.",
|
|
@@ -685,6 +685,81 @@ var recent_changes_generated_default = {
|
|
|
685
685
|
"id": "supabase-key-migration",
|
|
686
686
|
"url": "https://supabase.com/docs/guides/getting-started/migrating-to-new-api-keys",
|
|
687
687
|
"notes": "Create new keys alongside legacy; replace frontend anon with publishable and backend service_role with secret. Check components then disable legacy keys. Grant/RLS behavior retained, and key switch doesn't fix access policy."
|
|
688
|
+
},
|
|
689
|
+
{
|
|
690
|
+
"id": "next-security-oct-2026",
|
|
691
|
+
"url": "https://nextjs.org/blog/nextjs-security-update-october-14-2026",
|
|
692
|
+
"notes": "Dated October 14, 2026. Out-of-band release fixing two critical remote code execution issues (Image Optimization with SVG; use cache returning typed arrays) and a high-severity Server Actions denial of service. Fixed in next 16.4.1 and 15.5.28."
|
|
693
|
+
},
|
|
694
|
+
{
|
|
695
|
+
"id": "stripe-endive-checkout",
|
|
696
|
+
"url": "https://docs.stripe.com/changelog/endive/2026-09-30/remove-payment-method-types-checkout-sessions",
|
|
697
|
+
"notes": "API version 2026-09-30.endive removes the writable payment_method_types parameter from Checkout Session create; requests that send it fail with payment_method_types_no_longer_supported."
|
|
698
|
+
},
|
|
699
|
+
{
|
|
700
|
+
"id": "stripe-node-endive-pin",
|
|
701
|
+
"url": "https://raw.githubusercontent.com/stripe/stripe-node/master/CHANGELOG.md",
|
|
702
|
+
"notes": "stripe-node 23.0.0 (2026-09-30) pins API version 2026-09-30.endive, so a new install of the stripe package sends Endive requests unless apiVersion says otherwise."
|
|
703
|
+
},
|
|
704
|
+
{
|
|
705
|
+
"id": "openai-deprecations",
|
|
706
|
+
"url": "https://developers.openai.com/api/docs/deprecations",
|
|
707
|
+
"notes": "Shutdowns: legacy GPT snapshots on October 23, 2026 (gpt-3.5-turbo, gpt-4, gpt-4-turbo, o1, o3-mini, o4-mini, gpt-4.1-nano and others); GPT-5 and o3 snapshots on December 11, 2026; dated GPT-4o, GPT-4o mini and GPT-4.1 snapshots on January 14, 2027. Each row names a replacement."
|
|
708
|
+
},
|
|
709
|
+
{
|
|
710
|
+
"id": "lovable-changelog-models",
|
|
711
|
+
"url": "https://docs.lovable.dev/changelog",
|
|
712
|
+
"notes": "Lovable AI retired google/gemini-2.5-pro, -flash and -flash-lite on October 20, 2026 (requests rerouted); google/gemini-3.6-flash stops working November 19, 2026 and google/gemini-3.7-flash January 28, 2027; replacement google/gemini-3.8-flash."
|
|
713
|
+
},
|
|
714
|
+
{
|
|
715
|
+
"id": "anthropic-model-deprecations",
|
|
716
|
+
"url": "https://platform.claude.com/docs/en/about-claude/model-deprecations",
|
|
717
|
+
"notes": "claude-sonnet-4-5-20250929 retires on the Claude API on November 30, 2026 (replacement claude-sonnet-5-5). Earlier retirements include the claude-3-5-sonnet models, claude-3-7-sonnet-20250219, claude-3-5-haiku-20241022, claude-3-haiku-20240307 and the Claude 4 and 4.1 Opus and Sonnet snapshots. Bedrock and Vertex follow their own schedules."
|
|
718
|
+
},
|
|
719
|
+
{
|
|
720
|
+
"id": "supabase-claude-issued-mcp-auth-post",
|
|
721
|
+
"url": "https://supabase.com/blog/claude-issued-enterprise-managed-auth-for-mcp",
|
|
722
|
+
"notes": "Published November 3, 2026. Claude can issue the ID-JAG identity assertion for the Supabase MCP server when the IdP does not support the MCP Enterprise-Managed Authorization extension. Supabase side generally available to Team and Enterprise organizations with SSO; Claude auto-connect is a beta for Claude Team and Enterprise. Disabling a member in the IdP no longer cuts off access; tokens already issued stay valid until they expire."
|
|
723
|
+
},
|
|
724
|
+
{
|
|
725
|
+
"id": "supabase-enterprise-mcp-authorization",
|
|
726
|
+
"url": "https://supabase.com/docs/guides/platform/sso/enterprise-mcp-authorization",
|
|
727
|
+
"notes": "Setup guide, section Use Claude as the ID-JAG issuer. Supabase trusts one issuer URL per SSO provider, so saving the Claude URL makes Supabase reject every ID-JAG the IdP issues; each issuer URL serves one Supabase organization; emails must match (case-insensitive, no aliases or plus-addresses); under SCIM, Claude removes members only when the directory deletes them. No dates on the page."
|
|
728
|
+
},
|
|
729
|
+
{
|
|
730
|
+
"id": "next-security-2026-11-03-source",
|
|
731
|
+
"url": "https://nextjs.org/blog/november-2026-security-release",
|
|
732
|
+
"notes": "Read official announcement on 2026-11-05. Publication date and feature constraints verified; no provider or runtime check."
|
|
733
|
+
},
|
|
734
|
+
{
|
|
735
|
+
"id": "supabase-cli-v3-local-default-source",
|
|
736
|
+
"url": "https://supabase.com/changelog/supabase-cli-v3",
|
|
737
|
+
"notes": "Read official announcement on 2026-11-05. Publication date and feature constraints verified; no provider or runtime check."
|
|
738
|
+
},
|
|
739
|
+
{
|
|
740
|
+
"id": "supabase-cli-v3-migration-guide",
|
|
741
|
+
"url": "https://supabase.com/docs/guides/local-development/cli/migrating-to-v3",
|
|
742
|
+
"notes": "Migration guide updated November 3, 2026. Confirms local targets, hosted consent, removed inbucket sections, config precedence and auth.sms.enable_confirmations behavior. Guide update and default-install announcement dates are distinct."
|
|
743
|
+
},
|
|
744
|
+
{
|
|
745
|
+
"id": "vercel-security-review-beta-source",
|
|
746
|
+
"url": "https://vercel.com/changelog/vercel-security-review-public-beta",
|
|
747
|
+
"notes": "Read official announcement on 2026-11-05. Publication date and feature constraints verified; no provider or runtime check."
|
|
748
|
+
},
|
|
749
|
+
{
|
|
750
|
+
"id": "vercel-cli-doctor-source",
|
|
751
|
+
"url": "https://vercel.com/changelog/vercel-cli-now-diagnoses-setup-problems-with-vercel-doctor",
|
|
752
|
+
"notes": "Read official announcement on 2026-11-05. Publication date and feature constraints verified; no provider or runtime check."
|
|
753
|
+
},
|
|
754
|
+
{
|
|
755
|
+
"id": "clerk-native-minimum-version-source",
|
|
756
|
+
"url": "https://clerk.com/changelog/2026-11-03-minimum-app-version",
|
|
757
|
+
"notes": "Read official announcement on 2026-11-05. Publication date and feature constraints verified; no provider or runtime check."
|
|
758
|
+
},
|
|
759
|
+
{
|
|
760
|
+
"id": "vercel-workflow-atomic-start-source",
|
|
761
|
+
"url": "https://vercel.com/changelog/atomic-start-hooks-in-the-workflow-sdk",
|
|
762
|
+
"notes": "Read official announcement on 2026-11-05. Publication date and feature constraints verified; no provider or runtime check."
|
|
688
763
|
}
|
|
689
764
|
],
|
|
690
765
|
"entries": [
|
|
@@ -817,6 +892,215 @@ var recent_changes_generated_default = {
|
|
|
817
892
|
"supabase-key-migration"
|
|
818
893
|
],
|
|
819
894
|
"limitations": "No key/account/provider inspection, rotation, or live request. Switching key formats does not fix missing grants or RLS policies."
|
|
895
|
+
},
|
|
896
|
+
{
|
|
897
|
+
"id": "next-security-2026-10-14",
|
|
898
|
+
"provider": "nextjs",
|
|
899
|
+
"date": "2026-10-14",
|
|
900
|
+
"dateKind": "announced",
|
|
901
|
+
"dateNote": "October announcement date. The November 3 follow-up is tracked separately as next-security-2026-11-03; October patch status does not clear November issues.",
|
|
902
|
+
"whatChanged": "Next.js fixed two critical remote code execution vulnerabilities (Image Optimization with SVG input, and use cache returning typed arrays) and a high-severity Server Actions denial of service. Affected: next 10.0.0 to 15.5.27 and 16.0.0 to 16.4.0.",
|
|
903
|
+
"errorText": null,
|
|
904
|
+
"errorTextKind": "not_documented",
|
|
905
|
+
"symptom": "No error: an unpatched app keeps working while exposed.",
|
|
906
|
+
"fix": "Upgrade next to 16.4.1 (16.x) or 15.5.28 (15.x and older lines), reinstall so the lockfile resolves the patched version, rebuild and redeploy. A caret range in package.json may already resolve to a patched version; the lockfile decides.",
|
|
907
|
+
"officialSource": "https://nextjs.org/blog/nextjs-security-update-october-14-2026",
|
|
908
|
+
"sourceIds": [
|
|
909
|
+
"next-security-oct-2026"
|
|
910
|
+
],
|
|
911
|
+
"limitations": "Version ranges come from the GitHub advisories linked by the post. A repo shows the declared range; only the lockfile or npm ls next shows the installed version. Whether Vercel-hosted deployments are shielded is not stated."
|
|
912
|
+
},
|
|
913
|
+
{
|
|
914
|
+
"id": "stripe-endive-payment-method-types",
|
|
915
|
+
"provider": "stripe",
|
|
916
|
+
"date": "2026-09-30",
|
|
917
|
+
"dateKind": "effective",
|
|
918
|
+
"dateNote": "Applies to requests on API version 2026-09-30.endive or later. stripe-node 23.0.0 pins that version, so a fresh npm install stripe gets it.",
|
|
919
|
+
"whatChanged": "API version Endive removes the writable payment_method_types parameter from Checkout Session create and from PaymentIntent and SetupIntent create, update and confirm. Requests that still send it fail.",
|
|
920
|
+
"errorText": "payment_method_types_no_longer_supported",
|
|
921
|
+
"errorTextKind": "official_documentation_example",
|
|
922
|
+
"errorCode": "payment_method_types_no_longer_supported",
|
|
923
|
+
"symptom": "Checkout or payment creation returns HTTP 400 after upgrading the stripe package.",
|
|
924
|
+
"fix": "Remove payment_method_types from those calls. Rely on dynamic payment methods set in the Dashboard, or use allowed_payment_method_types or excluded_payment_method_types. Test in test mode; reading payment_method_types from a response is unaffected.",
|
|
925
|
+
"officialSource": "https://docs.stripe.com/changelog/endive/2026-09-30/remove-payment-method-types-checkout-sessions",
|
|
926
|
+
"sourceIds": [
|
|
927
|
+
"stripe-endive-checkout",
|
|
928
|
+
"stripe-node-endive-pin"
|
|
929
|
+
],
|
|
930
|
+
"limitations": "A client built with an explicit pre-Endive apiVersion is not affected, and a raw REST call uses the account default version, which the repo does not show."
|
|
931
|
+
},
|
|
932
|
+
{
|
|
933
|
+
"id": "openai-model-shutdowns-2026",
|
|
934
|
+
"provider": "openai",
|
|
935
|
+
"date": "2026-12-11",
|
|
936
|
+
"dateKind": "effective",
|
|
937
|
+
"dateNote": "Three dates: legacy GPT snapshots shut down 2026-10-23; GPT-5 and o3 snapshots on 2026-12-11; dated GPT-4o, GPT-4o mini and GPT-4.1 snapshots on 2027-01-14.",
|
|
938
|
+
"whatChanged": "OpenAI removes these model IDs from the API: gpt-3.5-turbo, gpt-4, gpt-4-turbo, o1, o3-mini, o4-mini, gpt-4.1-nano and gpt-image-1 (2026-10-23); gpt-5, gpt-5-mini, gpt-5-nano, gpt-5-pro, o3 and o3-pro (2026-12-11); gpt-4o-2024-08-06, gpt-4o-2024-11-20, gpt-4o-mini-2024-07-18 and gpt-4.1-2025-04-14 (2027-01-14). Requests to a removed model fail.",
|
|
939
|
+
"errorText": null,
|
|
940
|
+
"errorTextKind": "not_documented",
|
|
941
|
+
"symptom": "An AI feature that worked starts failing with a model not found error after the shutdown date.",
|
|
942
|
+
"fix": "Replace each model ID with the replacement the deprecations page lists, then run the feature once and compare output and cost.",
|
|
943
|
+
"officialSource": "https://developers.openai.com/api/docs/deprecations",
|
|
944
|
+
"sourceIds": [
|
|
945
|
+
"openai-deprecations"
|
|
946
|
+
],
|
|
947
|
+
"limitations": "Azure OpenAI deployments and OpenRouter-style openai/... IDs follow other schedules. The bare aliases gpt-4o and gpt-4o-mini are not on the page."
|
|
948
|
+
},
|
|
949
|
+
{
|
|
950
|
+
"id": "lovable-ai-gemini-retirements",
|
|
951
|
+
"provider": "lovable",
|
|
952
|
+
"date": "2026-11-19",
|
|
953
|
+
"dateKind": "effective",
|
|
954
|
+
"dateNote": "Gemini 2.5 models were retired on 2026-10-20 with requests rerouted; google/gemini-3.6-flash stops on 2026-11-19 and google/gemini-3.7-flash on 2027-01-28.",
|
|
955
|
+
"whatChanged": "Lovable AI retired google/gemini-2.5-pro, google/gemini-2.5-flash and google/gemini-2.5-flash-lite (rerouted to newer models, which changes cost and answers). google/gemini-3.6-flash and google/gemini-3.7-flash stop working on their dates. The replacement is google/gemini-3.8-flash.",
|
|
956
|
+
"errorText": null,
|
|
957
|
+
"errorTextKind": "not_documented",
|
|
958
|
+
"symptom": "AI answers or cost change after 2026-10-20; requests to the 3.6 or 3.7 Flash model fail after their dates.",
|
|
959
|
+
"fix": "Change the model string to google/gemini-3.8-flash (or ask Lovable to), redeploy the edge function, and check one real request.",
|
|
960
|
+
"officialSource": "https://docs.lovable.dev/changelog",
|
|
961
|
+
"sourceIds": [
|
|
962
|
+
"lovable-changelog-models"
|
|
963
|
+
],
|
|
964
|
+
"limitations": "The same google/... strings sent through OpenRouter or another gateway follow that gateway, not Lovable."
|
|
965
|
+
},
|
|
966
|
+
{
|
|
967
|
+
"id": "anthropic-claude-model-retirements",
|
|
968
|
+
"provider": "anthropic",
|
|
969
|
+
"date": "2026-11-30",
|
|
970
|
+
"dateKind": "effective",
|
|
971
|
+
"dateNote": "claude-sonnet-4-5-20250929 retires on 2026-11-30 (deprecated 2026-09-30). Several older Claude models are already retired.",
|
|
972
|
+
"whatChanged": "Requests to a retired Claude model fail. claude-sonnet-4-5-20250929 retires on 2026-11-30 (replacement claude-sonnet-5-5). Already retired: the claude-3-5-sonnet models, claude-3-7-sonnet-20250219, claude-3-5-haiku-20241022, claude-3-haiku-20240307, claude-sonnet-4-20250514, claude-opus-4-20250514 and claude-opus-4-1-20250805.",
|
|
973
|
+
"errorText": null,
|
|
974
|
+
"errorTextKind": "not_documented",
|
|
975
|
+
"symptom": "An AI feature that worked starts failing after the retirement date.",
|
|
976
|
+
"fix": "Switch each model ID to the replacement on the deprecations page and test the output.",
|
|
977
|
+
"officialSource": "https://platform.claude.com/docs/en/about-claude/model-deprecations",
|
|
978
|
+
"sourceIds": [
|
|
979
|
+
"anthropic-model-deprecations"
|
|
980
|
+
],
|
|
981
|
+
"limitations": "Amazon Bedrock and Google Vertex AI model IDs follow those platforms. The undated alias claude-sonnet-4-5 is not in the table."
|
|
982
|
+
},
|
|
983
|
+
{
|
|
984
|
+
"id": "supabase-mcp-claude-issued-auth",
|
|
985
|
+
"provider": "supabase",
|
|
986
|
+
"date": "2026-11-03",
|
|
987
|
+
"dateKind": "announced",
|
|
988
|
+
"dateNote": "Supabase blog post date. The Supabase side is generally available to Team and Enterprise organizations with SSO; Claude's side (Claude-issued auth, auto-connect) is a beta for Claude Team and Enterprise.",
|
|
989
|
+
"whatChanged": "Enterprise-managed authorization for the Supabase MCP server no longer needs an IdP that supports the MCP extension: Claude can sign the ID-JAG identity assertion instead. A Claude admin copies Claude's per-organization issuer URL from Organization settings > Connectors > Supabase > Managed authorization, a Supabase owner or admin pastes it into SSO > Advanced settings > ID-JAG Issuer, and members in the chosen Claude roles then see Supabase connected with no sign-in or consent screen.",
|
|
990
|
+
"errorText": null,
|
|
991
|
+
"errorTextKind": "not_documented",
|
|
992
|
+
"errorCode": null,
|
|
993
|
+
"symptom": "After the Claude issuer URL is saved, Supabase rejects every ID-JAG the IdP issues, so other AI tools that use the IdP for managed authorization lose access until the IdP URL is restored. A member disabled only in the IdP keeps access.",
|
|
994
|
+
"fix": "Before saving the Claude issuer URL, list the tools that use the IdP's ID-JAG: Supabase trusts one issuer per SSO provider, and each issuer URL serves one Supabase organization. Members need the same email in Claude and Supabase (case-insensitive, no aliases or plus-addresses) and one SSO sign-in to Supabase. To offboard, remove the member from both the Supabase and the Claude organization; tokens already issued stay valid until they expire. Remove a former member from Supabase before reusing their email. Under SCIM, Claude removes members only when the directory deletes them, not when it suspends them.",
|
|
995
|
+
"officialSource": "https://supabase.com/blog/claude-issued-enterprise-managed-auth-for-mcp",
|
|
996
|
+
"sourceIds": [
|
|
997
|
+
"supabase-claude-issued-mcp-auth-post",
|
|
998
|
+
"supabase-enterprise-mcp-authorization"
|
|
999
|
+
],
|
|
1000
|
+
"limitations": "Dashboard configuration only: repository files cannot show SSO, the issuer URL, organization membership or connector roles. Claude checks organization membership and the account email, not IdP sign-in, MFA or Supabase sign-in rules. Neither source gives a token lifetime."
|
|
1001
|
+
},
|
|
1002
|
+
{
|
|
1003
|
+
"id": "next-security-2026-11-03",
|
|
1004
|
+
"provider": "nextjs",
|
|
1005
|
+
"date": "2026-11-03",
|
|
1006
|
+
"symptom": "Depending on enabled features and hosting, an older release can disclose cached data or cookies, poison caches, or mishandle responses. Version alone does not prove exposure.",
|
|
1007
|
+
"fix": "Upgrade the installed/locked next dependency to 16.4.5 or 15.5.29 for its release line, rebuild and test. Read the individual advisory conditions for Cache Components, self-hosting, Edge routes and image backends.",
|
|
1008
|
+
"dateKind": "announced",
|
|
1009
|
+
"dateNote": "Official announcement publication date, not proof of rollout to this project.",
|
|
1010
|
+
"whatChanged": "Next.js released 16.4.5 and 15.5.29 for seven security issues involving cache isolation, self-hosted response handling, Edge cookie headers and image decoding.",
|
|
1011
|
+
"errorText": null,
|
|
1012
|
+
"errorTextKind": "not_documented",
|
|
1013
|
+
"officialSource": "https://nextjs.org/blog/november-2026-security-release",
|
|
1014
|
+
"sourceIds": [
|
|
1015
|
+
"next-security-2026-11-03-source"
|
|
1016
|
+
],
|
|
1017
|
+
"limitations": "A declaration is not an installed or deployed version. The notice does not establish universal exploitability; hosting and feature preconditions differ per issue."
|
|
1018
|
+
},
|
|
1019
|
+
{
|
|
1020
|
+
"id": "supabase-cli-v3-local-default",
|
|
1021
|
+
"provider": "supabase",
|
|
1022
|
+
"date": "2026-11-04",
|
|
1023
|
+
"symptom": "CLI automation may target local instead of hosted or stop for consent; old inbucket configuration prevents local commands from starting.",
|
|
1024
|
+
"fix": "Inspect installed CLI help and pin the intended version. Before upgrading automation, review every target: explicitly select --remote for intended hosted database work and deliberately authorize each hosted mutation before adding --yes. Rename [inbucket] to [local_smtp] and review environment overrides and pg-delta output.",
|
|
1025
|
+
"dateKind": "announced",
|
|
1026
|
+
"dateNote": "November 4 default-install announcement, distinct from the November 2 v3.0.0 release and November 3 migration-guide update. Not proof of rollout to this project.",
|
|
1027
|
+
"whatChanged": "Supabase CLI v3 is now the default install. Database commands target local by default; hosted mutations require consent, including --yes when unattended. Config precedence changes and [inbucket] becomes [local_smtp].",
|
|
1028
|
+
"errorText": null,
|
|
1029
|
+
"errorTextKind": "not_documented",
|
|
1030
|
+
"officialSource": "https://supabase.com/changelog/supabase-cli-v3",
|
|
1031
|
+
"sourceIds": [
|
|
1032
|
+
"supabase-cli-v3-local-default-source",
|
|
1033
|
+
"supabase-cli-v3-migration-guide"
|
|
1034
|
+
],
|
|
1035
|
+
"limitations": "CLI migration guidance only. Hosted projects do not change merely because v3 exists. No command or mutation was executed; a repo cannot establish which CLI a CI runner installs."
|
|
1036
|
+
},
|
|
1037
|
+
{
|
|
1038
|
+
"id": "vercel-security-review-beta",
|
|
1039
|
+
"provider": "vercel",
|
|
1040
|
+
"date": "2026-11-03",
|
|
1041
|
+
"symptom": "Informational capability announcement, not a breaking change or a finding that this repository is vulnerable.",
|
|
1042
|
+
"fix": "If the team is eligible, review Security Review configuration and inspect commit-specific findings in the dashboard. Proposed fixes still require review; this feed does not enable the service.",
|
|
1043
|
+
"dateKind": "announced",
|
|
1044
|
+
"dateNote": "Official announcement publication date, not proof of rollout to this project.",
|
|
1045
|
+
"whatChanged": "Vercel Security Review entered public beta for Pro and Enterprise teams. Once enabled, pushes to connected GitHub repositories trigger reviews; findings appear in the Vulnerabilities dashboard.",
|
|
1046
|
+
"errorText": null,
|
|
1047
|
+
"errorTextKind": "not_documented",
|
|
1048
|
+
"officialSource": "https://vercel.com/changelog/vercel-security-review-public-beta",
|
|
1049
|
+
"sourceIds": [
|
|
1050
|
+
"vercel-security-review-beta-source"
|
|
1051
|
+
],
|
|
1052
|
+
"limitations": "Repository config does not prove plan eligibility, enablement, a completed security review, or absence of vulnerabilities. No account or GitHub integration was changed."
|
|
1053
|
+
},
|
|
1054
|
+
{
|
|
1055
|
+
"id": "vercel-cli-doctor",
|
|
1056
|
+
"provider": "vercel",
|
|
1057
|
+
"date": "2026-11-03",
|
|
1058
|
+
"symptom": "Informational diagnostic option when an agent encounters a Vercel CLI setup problem; a repo signal is not evidence of such a problem.",
|
|
1059
|
+
"fix": "With a CLI version supporting it, run vercel doctor --json and inspect individual statuses before taking further action. Doctor does not log in, prompt, or link a project.",
|
|
1060
|
+
"dateKind": "announced",
|
|
1061
|
+
"dateNote": "Official announcement publication date, not proof of rollout to this project.",
|
|
1062
|
+
"whatChanged": "Vercel CLI adds doctor with structured JSON statuses and suggested commands for installation, identity/team, project linking, configuration and status incidents.",
|
|
1063
|
+
"errorText": null,
|
|
1064
|
+
"errorTextKind": "not_documented",
|
|
1065
|
+
"officialSource": "https://vercel.com/changelog/vercel-cli-now-diagnoses-setup-problems-with-vercel-doctor",
|
|
1066
|
+
"sourceIds": [
|
|
1067
|
+
"vercel-cli-doctor-source"
|
|
1068
|
+
],
|
|
1069
|
+
"limitations": "This matcher never invokes doctor or checks login, linking, team membership, incidents or installed global tooling. Suggested remedial commands require their own review."
|
|
1070
|
+
},
|
|
1071
|
+
{
|
|
1072
|
+
"id": "clerk-native-minimum-version",
|
|
1073
|
+
"provider": "clerk",
|
|
1074
|
+
"date": "2026-11-03",
|
|
1075
|
+
"symptom": "Users below an enabled minimum must update. Earlier SDKs may not show the update screen; older iOS SDKs can show an error.",
|
|
1076
|
+
"fix": "Release a compatible build before setting a minimum: Clerk iOS 1.7.0, Android 1.4.0 or @clerk/expo 4.15.0 or later, plus required platform setup. Review the Dashboard minimum separately.",
|
|
1077
|
+
"dateKind": "announced",
|
|
1078
|
+
"dateNote": "Official announcement publication date, not proof of rollout to this project.",
|
|
1079
|
+
"whatChanged": "Clerk adds Dashboard minimum-version enforcement for native apps. Compatible SDKs display an update screen while retaining sign-in state.",
|
|
1080
|
+
"errorText": null,
|
|
1081
|
+
"errorTextKind": "not_documented",
|
|
1082
|
+
"officialSource": "https://clerk.com/changelog/2026-11-03-minimum-app-version",
|
|
1083
|
+
"sourceIds": [
|
|
1084
|
+
"clerk-native-minimum-version-source"
|
|
1085
|
+
],
|
|
1086
|
+
"limitations": "The matcher recognizes Expo package usage only, not native Swift/Kotlin projects. Dependency presence does not establish the installed SDK, released build, store availability, or Dashboard configuration."
|
|
1087
|
+
},
|
|
1088
|
+
{
|
|
1089
|
+
"id": "vercel-workflow-atomic-start",
|
|
1090
|
+
"provider": "vercel",
|
|
1091
|
+
"date": "2026-11-04",
|
|
1092
|
+
"symptom": "Concurrent requests can start duplicate work when a hook lookup and run admission are separate operations.",
|
|
1093
|
+
"fix": "Review legacy getHookByToken followed by start. Use start with experimental_hook: { token } for atomic admission; handle HookConflictError and resumeHook to route a duplicate payload to the existing run. Verify application-specific concurrency behavior.",
|
|
1094
|
+
"dateKind": "announced",
|
|
1095
|
+
"dateNote": "Official announcement publication date, not proof of rollout to this project.",
|
|
1096
|
+
"whatChanged": "Workflow SDK can atomically claim a hook when admitting a run. The earlier lookup-then-start approach has a duplicate-start race.",
|
|
1097
|
+
"errorText": null,
|
|
1098
|
+
"errorTextKind": "not_documented",
|
|
1099
|
+
"officialSource": "https://vercel.com/changelog/atomic-start-hooks-in-the-workflow-sdk",
|
|
1100
|
+
"sourceIds": [
|
|
1101
|
+
"vercel-workflow-atomic-start-source"
|
|
1102
|
+
],
|
|
1103
|
+
"limitations": "Same-file calls are a review signal, not proof of a race. This feed does not install a Workflow SDK, execute workflows or prove application idempotency."
|
|
820
1104
|
}
|
|
821
1105
|
]
|
|
822
1106
|
}
|
|
@@ -1876,7 +2160,7 @@ async function boundedJson2(response2) {
|
|
|
1876
2160
|
}
|
|
1877
2161
|
|
|
1878
2162
|
// ../cli/src/version.ts
|
|
1879
|
-
var VERSION = "1.7.
|
|
2163
|
+
var VERSION = "1.7.9";
|
|
1880
2164
|
|
|
1881
2165
|
// ../cli/src/commands/account.ts
|
|
1882
2166
|
var loginNext = `npx -y viberaven@${VERSION} login --json`;
|
|
@@ -2221,7 +2505,7 @@ function mcpVersion() {
|
|
|
2221
2505
|
} catch {
|
|
2222
2506
|
}
|
|
2223
2507
|
}
|
|
2224
|
-
found ??= true ? "1.7.
|
|
2508
|
+
found ??= true ? "1.7.9" : void 0;
|
|
2225
2509
|
if (!found || !PLAIN_VERSION.test(found)) {
|
|
2226
2510
|
throw new Error(`Could not read a valid ${MCP_PACKAGE} version (got ${JSON.stringify(found)}), so the matching ${CLI_PACKAGE} cannot be pinned.`);
|
|
2227
2511
|
}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@viberaven/mcp",
|
|
3
|
-
"version": "1.7.
|
|
3
|
+
"version": "1.7.9",
|
|
4
4
|
"description": "MCP server for VibeRaven: lets Claude Code, Cursor and Codex run the Supabase RLS and security check on an AI-built Vercel + Supabase app and read the findings.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"author": "VibeRaven",
|